Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<79218202D4B9D4118A290002A508E13B79C3B8@pnzexchange.pharos-intranet.co.nz>
From:	Ross Smith <rosss AT pharos DOT co DOT nz>
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject:	RE: Mixing / and \ path separators
Date:	Fri, 14 Mar 2003 08:46:13 +1300
MIME-Version:	1.0

> From: Christopher Faylor [mailto:cgf-cygwin AT cygwin DOT com]
> 
> On Wed, Mar 12, 2003 at 11:08:27PM +0100, Anton Ertl wrote:
> >
> >If so, how should I deal with path names where parts of the path come
> >from ordinary windows users?
> 
> Either tell your Windows users to use forward slashes, tell them to
> specify the path name using windows specs like f:\cygwin\foo\bar,
> or change the backslashes to slashes.

Wouldn't cygwin_conv_to_posix_path() and its relatives be a more
general solution?

-- 
Ross Smith ...................... Pharos Systems, Auckland, New Zealand

        "It's never too soon to start planning, and, in fact,
                it's usually too late." -- Chad Orzel

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -