Re: The case insensitive #include statement horror...
- From: "Tom Serface" <tserface@xxxxxxx>
- Date: Wed, 29 Nov 2006 08:43:17 -0800
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.
I don't know if this is useful to you or not, but have you seen the MainWin
toolkit?
http://www.ddj.com/184410913
Also, you can use a #pragma comment to warn the developer at run time or,
perhaps add a pre-build step that renames the .h files to what you would
expect them to be?
I know this doesn't directly answer the question. The real answer is I
don't think there is a #pragma to do what you'd like, although I think it
would be very useful. The real answer is for Windows programmers to become
more disciplined in how they type in filenames, but, um, like that's going
to happen.
tom
"Stephan Kuhagen" <nospam@xxxxxxxxxx> wrote in message
news:ekk55m$2b4$1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello
Sorry for crossposting. I'm not really sure, what is the right place for
the
question I have:
I'm managing a huge build system for multiple platforms (Win*, Linux,
MacOSX). Most of our programmers work on Windows and seem to be unable to
learn the difference between upper and lower case characters in #include.
So most time the thing works on Windows, but fails on the others. Although
they get mails when a project fails, the errors either do not get fixed or
they re-appear after every change... This is _really annoying_ ! - Does
anyone here know a switch, pragma or other trick to make the
Microsoft-Compilers (VC6 and up) case-sensitive in #include-statements and
throw an error on wrong case?
"Thanks for not shooting me"
Regards
Stephan Kuhagen
.
- Follow-Ups:
- Re: The case insensitive #include statement horror...
- From: Stephan Kuhagen
- Re: The case insensitive #include statement horror...
- Prev by Date: Re: class layout and dummy template parameter
- Next by Date: Re: Possible MSVC8 bug?
- Previous by thread: Recieiving an arrray from VB
- Next by thread: Re: The case insensitive #include statement horror...
- Index(es):
Relevant Pages
|