OT: DOS/Windows and slashes (was Re: Windows XP Pro and PossiblefilePro Bug)

[Fairlight]

You'll never BELIEVE what Kenneth Brody said here...:
> 
> What about typing "print" and having an "f" magically appear after it?

Same as "though" turning into "thought" and "ever" turning into "every".  I
do those all the time as well.  Force-of-habit typing.

> You can escape the slash all you want.  All that happens is that you end
> up with a slash, which is built into the kernel as the path separator.
> It's not possible to get a filename with a '/' or '\0' in it.  (Well, you
> could theoretically place a '/' in a filename with a raw disk editor, but
> I have no idea if you could ever access it.)

Hmmm...just tried it from perl with "bl\0ip" and ended up with a file "bl".
It does indeed truncate it, which makes sense knowing how "strings" are
handled in C.  NULL not mattering is something you can really come to like
in perl--where you can use it as a delimiter in strings if you like.

Well, two characters not being usable in filenames isn't a huge loss.  I
suppose it's one of those quirks I wasn't expecting because I'd never tried
it.  I figured if you could escape a ^H and the like (a perrenial favourite
of people trying to hide warez directories), you should be able to handle a
slash with relative ease.  Apparently not.  Thanks for the tip about NULL
as well, Ken.

mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!

Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html