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.
--
Ambassador Trentino: I've said enough. I'm a man of few words.
Rufus T. Firefly: I'm a man of one word: scram!
--Duck Soup John Cowan <[EMAIL PROTECTED]>
_______________________________________________
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
