delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2003/06/03/18:28:08

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: <002101c32a1f$6060df60$78d96f83@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "Greg Fenton" <greg_fenton AT yahoo DOT com>, <cygwin AT cygwin DOT com>
References: <20030603220046 DOT 97377 DOT qmail AT web40605 DOT mail DOT yahoo DOT com>
Subject: Re: Path separator
Date: Tue, 3 Jun 2003 23:27:54 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Cam-ScannerAdmin: mail-scanner-support AT ucs DOT cam DOT ac DOT uk
X-Cam-AntiVirus: Not scanned
X-Cam-SpamDetails:

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.


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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019