[M3devel] FW: more path stuff, sorry

[Jay]

[truncated]...


From: jayk123 at hotmail.comTo: rcoleburn at scires.com; m3devel at elegosoft.comSubject: RE: [M3devel] more path stuff, sorryDate: Tue, 22 Apr 2008 04:19:52 +0000


There's no dependency, no linkage. Just a few simple string operations.I'll probably remove it tonight. Modula-3 has a split personality no matter what, in that it calls into very varying underlying layers, often trafficing in their specific data formats.It's just that it can strive to aid portability between them or not, by accepting either input and massaging it to work, vs. passing it along "unchanged" (well, that's not what happens actually). If there were no ambiguous cases and the Posix systems on Windows were consistent in their conventions, I'd be more for it. But the ambiguity and varying Posix conventions weaken the case tremendously.  - Jay


Date: Mon, 21 Apr 2008 23:14:00 -0400From: rcoleburn at scires.comTo: m3devel at elegosoft.comSubject: Re: [M3devel] more path stuff, sorry
I concur wholeheartedly.  I absolutely DO NOT want native NT386 to have any knowledge of or dependency on Cygwin.
Regards,
Randy>>> Tony Hosking <hosking at cs.purdue.edu> 4/21/2008 9:44 PM >>>


Why would native NT386 know anything at all about Cygwin.  I say just avoid split personalities like the plague.  Similarly, I'd be happy for NT386GNU (i.e., Cygwin?) to simply behave like a POSIX build (modulo native threads perhaps).

On Apr 21, 2008, at 7:15 PM, Jay wrote:

Maybe this is dubious.The question is, like, should native NT386 cm3 accept /cygdrive/c/foo and translate to c:\foo?Or trickier, /usr/bin/foo and translate to c:\cygwin\usr\bin\foo?And vice versa, should NT386GNU accept c:\foo?...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20080422/f567d728/attachment-0002.html>