Windows paths (was RE: re open and read commands)

[Bill Campbell]

On Mon, Dec 03, 2007, Kenneth Brody wrote:
>Quoting fp (Sun, 02 Dec 2007 08:35:19 -0700):
>
>> Mike posted:
>>
>>>
>>> the following line gives me a syntax error
>>>
>>> import ascii ifile = c:\imagelist.wri r=\n
>>
>> Yeah, just add  f=\n  at end of line.  I do not use
>> WIN version of filePro but I thought you still needed
>> to use forward slash for paths not backslash ... ???
>
>The Windows (and DOS) versions of filePro have always allowed either
>slash in filenames.  This is because MS-DOS and Windows have always
>allowed either slash.

I think it's only command.com that requires the backward slashes, a relic
of the fact that MS-DOS was basically a port of CP/M to the 80x86 chip, and
CP/M used forward slashes for options, much like *nix uses ``-''.  About
the only thing different between the earliest versions of M$-DOS and CP/M
was that CP/M used the PIP command to copy files with the destination file
as the first argument, and M$-DOS used COPY with the arguments in logical
order.

Bill
--
INTERNET:   bill at celestial.com  Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/  PO Box 820; 6641 E. Mercer Way
FAX:            (206) 232-9186  Mercer Island, WA 98040-0820; (206) 236-1676

Perhaps, when committing your first federal crime, it would be unwise to
slap your name and address on it and mail it to 10,000 people. --Dogbert