Path separator

[Larry Hall]

Max Bowsher wrote:
> Greg Fenton wrote:
> 
>>--- Max Bowsher <maxb@ukf.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/