[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: A draft for a multibyte and multi-codepoint C string interface
On Mon, Apr 01, 2013 at 04:28:42PM +0200, tlaronde%polynum.com@localhost wrote:
> On Mon, Apr 01, 2013 at 10:18:37AM -0400, Thor Lancelot Simon wrote:
> > On Mon, Apr 01, 2013 at 10:29:38AM +0200, tlaronde%polynum.com@localhost
> > wrote:
> > >
> > > There is a simple solution, the one developed by Ken Thompson and al.
> > > from the Bell Labs: UTF-8. As long as the system is concerned, the
> > > filenames should be octets strings (UTF-8) and the same filename
> > > is the exact same string. No semantics at all. (I simply hate
> > > filesystem that are case sensitive, and I simply don't want the
> > > disease to go any further.
> > I agree: the only think I can think of that's a worse idea than a case
> > insensitive file system is a culturally sensitive filesystem.
> You automatically corrected my typo: I did mean I hate a "case
> insensitive" filesystem. But it should be obvious... I hope.
I think the filesystem should correct both of our typos. And all others!
Heaven forfend anyone should want the kernel to treat a byte string as
a byte string, and the result of creating a file be that a file with that
name actually shows up when the application reads the directory it put
Think of the opportunities for application misbehavior and programmer
error that will be missed if the kernel simply treats byte strings as
Main Index |
Thread Index |