Re: The case insensitive #include statement horror...

William DePalo [MVP VC++] wrote:

different people, one might expect that people think about how things can
work together and support each other.

Take that to its logical conclusion and you wind up with one operating
system designed by committee. No thank you.

Totally agree. That's why Multics failed and Unix was born. But for me the
logical conclusion would be not to design OS by committees but by engineers
and users depending on their needs and demands. After that, one should look
over the edge of it's own small part of the world, if there is something
out there, which one can learn from.

The Linux community does very much and reasonably well nowadays
in bringing some kind of Windows behaviour and Windows feeling to
the desktop.

And IMO that's why they will never succeed. They are perennial also-rans,
always playing catch-up.

Nah, come on, there are things on both side, where one can learn from each
other. Discussing starts going to the wrong direction that way. You
mentioned yourself the good idea of a filesystem with one tree hierarchy.

So it might be worth a thought how to help them getting their work done.

Whose work? <g>

In this case: mine. In other cases others. But I think, that is what
computers and OS (and developer tools) are made for: helping people their
work get done.

And it's surely the kind of solution, for which one gets
flamed in every advocacy community, if you do
something like that to any OS... ;-)

I'd hardly call this discussion a "flame".

No, surprisingly and pleasantly not. But go to one of the advocacy groups
somewhere on usenet (no matter which OS), and ask the same question and you
mostly get answers from people who seem to eat testosterone and drink
adrenaline for breakfast.

I don't think so. Win32 fs preserves the data, but it makes it simple to
lose them, if someone else puts a different file with a different name
into
the directory, if the names only differs in case.

I guess I still don't understand.

It preserves the data, because it preserves the case of the filenames - in
my thinking the filenames are also data, since for me they contain some
semantics in the spelling. But it makes it easy to lose this data, since
someone can easily overwrite this semantics accidently by writing another
file with a similar name, differing only in case.

Regards
Stephan

.

Loading