DOS/Windows and slashes (was Re: Windows XP Pro and Possible filePro Bug)

[Bill Vermillion]

On Sat, Dec 04 11:52 , while denying his reply is spam, Kenneth Brody 
prattled on endlessly saying: 

> Bob Stockler wrote:
> [...]
> > | Just a thought as I am not running sp2 here. Have you tried using windows back
> > | slash rather then the *nix right slash?

> > | This might be a problem with fp translating the slashes.

> > I am _positive_ that filePro is _not_ confused by one using
> > forward slashes on Windows filePro User Menu command lines.

> > I am fairly certain that filePro translates the / or \ in
> > pathnames in all it's stuff to be the one appropriate for
> > the OS.
> [...]

> DOS and Windows have always allowed both "/" and "\" as path
> separators. (Well, "always" as in "as long as DOS has supported
> paths in DOS 2.0".) It is command.com and some applications
> that do not allow "/" in paths, but the kernel itself has
> always allowed both.

And one reason that MS used the "\" for pathnames was that 
in their languages you had a choice of two switches, "/" or "-",
when specifiying command line options.

I remember when I was learning to use random access fixed length
records and having to specify two or three options on the file
names given.   You could use  /nnn  or -nnn in their BASIC
interpreter, and I vaguely recall the same thing in their Fortran.

I think I had MS BASIC 4.5 on my CP/M system.

Even in those days everyone thought MS was HUGELY overpriced.
If you wanted to distribute a program that you compiled you had
to have a run-time module to distribute with your program. 

I have a vague rememberance [is that correct English] that 
it was something like $50 for each 5.25 inch floppy that you had to
get from them.  And that >may< have been before MS moved
from Alberquerque, NM, to Redmond.  {I guess Bill was homesick for
the rain or his parents}

Bill

-- 
Bill Vermillion - bv @ wjv . com