Re: The case insensitive #include statement horror...
- From: "Tom Serface" <tserface@xxxxxxx>
- Date: Thu, 30 Nov 2006 07:21:25 -0800
Stephan,
One more thought... sort of in jest, but ...
Maybe you could force your Windows programs to compile all the programs on
the Unix system a few times so they can live through the pain. Or, have
them cross compile their code when they add new include files. I know this
is not automatic by any means, but maybe if they feel the Unix programmer's
pain they will be more careful to type in the correct names.
Tom
"Stephan Kuhagen" <nospam@xxxxxxxxxx> wrote in message
news:eklsn5$fg3$1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Tom Serface wrote:
I've found the whole thing of Windows not understanding case in filenames
to be challenging from the beginning having come from a Unix background.
"Challenging"... indeed. ;-)
I don't know if this is useful to you or not, but have you seen the
MainWin toolkit?
http://www.ddj.com/184410913
Thanks, that is an interesting article, but it has no solution for me.
Renaming all files to lower case can not be done, since we have rules
about
upper/lower case naming of files.
Regards
Stephan
.
- Follow-Ups:
- Re: The case insensitive #include statement horror...
- From: Carl Daniel [VC++ MVP]
- Re: The case insensitive #include statement horror...
- References:
- Re: The case insensitive #include statement horror...
- From: Tom Serface
- Re: The case insensitive #include statement horror...
- From: Stephan Kuhagen
- Re: The case insensitive #include statement horror...
- Prev by Date: Re: The case insensitive #include statement horror...
- Next by Date: Re: Checking whether redistributing DLLs is necessary
- Previous by thread: Re: The case insensitive #include statement horror...
- Next by thread: Re: The case insensitive #include statement horror...
- Index(es):
Relevant Pages
|
Loading