Am 01.03.2011 14:50, schrieb Nick Sabalausky:
"Steven Schveighoffer"<[email protected]> wrote in message
news:op.vrn2pooteav7ka@steve-laptop...
On Tue, 01 Mar 2011 08:13:33 -0500, Lars T. Kyllingstad
<[email protected]> wrote:
On Tue, 01 Mar 2011 08:02:44 -0500, Steven Schveighoffer wrote:
On Tue, 01 Mar 2011 04:16:36 -0500, Jonathan M Davis
<[email protected]> wrote:
I can understand if the path stuff
can't deal with / or \ in file names (that's probably not worth trying
to get to
work right), but it _should_ be able to handle directories with dots in
them and
files with no extension.
/ and \ are not legal in names on any filesystem that I know of.
-Steve
On a *NIX machine, try
touch "c:\\foo\\bar"
You may be surprised. ;)
bleh... that seems useless :) I purposely checked FAT before posting,
because I was sure Unix disallowed backslashes, I wanted to make sure FAT
didn't allow slashes.
Holy crap, something that DOS got right and Unix didn't!
Windows also handles files/paths with spaces a hell of a lot better than
Unix. This, despite the fact that Unix technically allowed them long before
Windows did. (I don't mean this as OS-bashing.)
It does? In what ways? In Unix you just have to escape spaces with
backslashes or put the filename in "" and you're done (bash
autocompletion does this). Don't think it's much simpler in Windows.
Filebrowsers (GUI or midnight commander etc) don't have any problems
with spaces either.
From this page: http://en.wikipedia.org/wiki/Filename, it appears that
really, the only disallowed character in unix filenames is '/'. Even '*'
is allowed as a filename. How... horrible.
I would actually feel very good to just simply not support such things. If
some unix user is going to use such awful filenames they can just deal with
the consequences. (And I'm *rarely* the kind of person to hold such a
viewpoint on software development matters.)
