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
X-Info: This message was accepted for relay by
	smtp03.mrf.mail.rcn.net as the sender used SMTP authentication
X-Trace: UmFuZG9tSVbPmg/ioL3bBkQkfDkDA6sZgtvTt5VIl5SYHqHSarTboURSgnX3ItRe
Message-ID: <3EDD5587.8060004@cygwin.com>
Date: Tue, 03 Jun 2003 22:12:23 -0400
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Greg Fenton <greg_fenton AT yahoo DOT com>
CC: cygwin AT cygwin DOT com
Subject: Re: Path separator
References: <20030603220046 DOT 97377 DOT qmail AT web40605 DOT mail DOT yahoo DOT com> <002101c32a1f$6060df60$78d96f83 AT pomello>
In-Reply-To: <002101c32a1f$6060df60$78d96f83@pomello>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Max Bowsher wrote:
> Greg Fenton wrote:
> 
>>--- 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)?
> 
> 
> Drastic oversimplification.
> 
> For example, one other thing you would need to do, is dynamically link to
> cygwin1.dll, which is not supported, because no one is sufficiently
> interested and has the time to research and write the code allow that to
> happen.


Max is right (surprised Max? ;-) )  But I want to point out something
else about what you've said.  If your main concern is paths, don't
convert '/' to '\'.  Windows understands both under the hood.  (Cygwin
does too but that's another matter).  However, this is the least of
your problems as Max clearly states.

-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746


--
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/