On Sun, 26 Oct 2008, John Cowan wrote:
Peter Bex scripsit:
It would be better to make the behaviour be system-specific, instead of
adding flags. On Windows, *always* treat slashes as backslashes. On Unix,
*only* accept slashes with no additional translation steps. (I'm not sure
Windows doesn't allow slashes in filenames, but I don't think it does)
Unix, of course, treats \ as an ordinary filename character. In Windows,
\ and / are interchangeable in system calls, although the command shell,
the desktop, and other file windows and dialogue boxes don't accept \
but only /. Inside Chicken, therefore, / is entirely portable and no
translation is ever necessary.
this is not strictly true; during installation of files (eg for chicken-setup)
some calls are done through the command shell. the / notation has certain
other concerns as well, mostly involving drive letter.
-elf
_______________________________________________
Chicken-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/chicken-users
