[PATCH] Support Cygwin network paths in tcl

Christopher Faylor cgf-use-the-mailinglist-please@cygwin.com
Mon Aug 7 20:18:00 GMT 2006


On Mon, Aug 07, 2006 at 08:37:13PM +0100, Thiemo Seufer wrote:
>Keith Seitz wrote:
>> Christopher Faylor wrote:
>> 
>> >My only non-insurmountable objection is that these aren't "cygwin network
>> >paths", they are "windows network paths".  I think that any comnents or
>> >ChangeLogs should be modified to reflect that fact.
>
>Well, that's not entirely correct. Windows network paths are already
>supported for native Windows builds.

How is a "native Windows build" pertinent to insight?

>The issue is to support them also for a unixlike build if the
>underlying OS is Windows.  Which means Cygwin.

Sorry but these are not "cygwin network paths".  They are "windows
network paths".  Cygwin doesn't have "network paths".  It just basically
passes on '//' and '\\' style paths on to Windows.  The '/' character is
understood by the Windows API just like the '\' character.

So, really, there should be no #ifdef __CYGWIN__ in the code either.

cgf



More information about the Insight mailing list