> Spoken as a true C programmer. However you are wrong. Case-preserving, but
> insensitive, is the CORRECT way for file systems. Capitalization should not
> matter for interpretation of a file name just as it doesn't matter for
> interpreting words in any human language. Capitalization should be for
> prettiness only.
> If it is so fundamentally broken, then why has no-one using all of those
> others OSes ever run into a problem with case-preserving file names.
Things get hairy when you have to deal with different character sets and
locales. Should "bl}b{r" and "BL]B[R" be regarded as the same file?
Converting an upper case alphabetic character to the corresponding lower case
character is not as simple as adding 0x20 to it, except if you are using only
7-bit ASCII.
NTFS carries a per-filesystem Upcase Table to map between lower and upper case
alphabetic characters.
Case sensitivity is a simple and efficient way of avoiding the can of worms.
Johan Myréen
jem@iki.fi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/