Path: utzoo!utgpu!watmath!mks!alex
From: alex@mks.UUCP (Alex White)
Newsgroups: comp.sys.ibm.pc
Subject: Re: pathnames
Message-ID: <667@mks.UUCP>
Date: 11 Feb 89 17:37:01 GMT
References: <2569@pegasus.ATT.COM> <3847@cbnews.ATT.COM> <662@mks.UUCP> <1623@stratus.UUCP>
Organization: Mortice Kern Systems, Waterloo, Ont.
Lines: 16

In article <1623@stratus.UUCP>, gbs@stratus.UUCP (George B. Smith) writes:
> In article <10353@ut-emx.UUCP> nather@ut-emx.UUCP (Ed Nather) writes:
> >
> >It would indeed.  Most of the MS-DOS utilities will accept either one,
> >but "subst" will not, and both MSC and Borland's linker demand backslashes.
> >A recent conversation about Borland's new debugger, which also demands
> >
> >"Well, OS2 doesn't allow it, so get used to backslashes."
Interestingly enough, MSC's interface ``cl'' accepts either - or /
for options.
It is also explicitly documented in their manuals, that / may be used
in #include filenames so that you can exchange programs with Xenix.
OS/2 has just made things worse - cmd.exe now takes `^' (the uparrow, cap)
as an escape character, doing what `\' has always done under unix.
OS/2 and DOS all continue to accept either slash in all system calls
interfacing to the kernel.