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: <20030603220046.97377.qmail@web40605.mail.yahoo.com>
Date: Tue, 3 Jun 2003 15:00:46 -0700 (PDT)
From: Greg Fenton <greg_fenton AT yahoo DOT com>
Subject: Re: Path separator
To: Max Bowsher <maxb AT ukf DOT net>, cygwin AT cygwin DOT com
In-Reply-To: <005801c32a16$fd886f50$78d96f83@pomello>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


--- Max Bowsher <maxb AT ukf DOT net> wrote:
> 
> No: Cygwin != _WIN32.
> 

No argument from me here.  :-)


> A native/Cygwin dual-mode binary sounds like a clever idea, but AFAIK
> has never been done before, and is probably ridiculously infeasible
on
> the balance of work/benefit.

I don't see that the amount of work is ridiculous at all.  Any portable
code will have a path-conversion (canonicalization) function in place
for any and all file system access.  That canonicalization should be
able to determine the PATH_SEPARATOR for the given environment.

For my code to support win32 and cygwin, I only need to know what the
PATH_SEPARATOR is for the current running environment.  It may not be
in Cygwin right now, but wouldn't this be a Good Thing (and benign for
those who want to ignore it)?

I'm still open to suggestions if there are any others.

greg_fenton.

=====
Greg Fenton
greg_fenton AT yahoo DOT com

__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/