Re: seduid scripts

[ersmith@netcom.com (Eric R. Smith)]

>> / -> \ mapping isn't going back into the kernel. Sorry.

>Fairy nuff Eric, but why ?


Basically, because we already have one path separator (\). Introducing
another one is messy, especially since GEMDOS has historically allowed
/ in file names (indeed many users have files with names like
"2/12/92". I realize that Unix aware people would never do such a silly
thing, but unfortunately lots of ST users are not Unix aware. If I were
designing TOS from scratch I would use / as the path separator, but
unfortunately it's much too late for that.

Also, by not using / for anything in the kernel, we provide a way to
represent Unix file names containing \; namely, a Posix library could
simply swap / and \ everywhere they occur in file names..