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

Tech-Archive recommends: Fix windows errors by optimizing your registry

Alexander Grigoriev wrote:

Try FILE_FLAG_POSIX_SEMANTICS for case sensitivity.

Thanks for the suggestion. I will have a look at it, but I do not want to
write a complete preprocessor. I only want #include statements with wrong
case to fail. - Parsing the source myself and checking the #include
statements is not really an option, because that would mean to write
parsers for nearly everything to be sure. E.g. the dsp-files for include
paths, macro expansion to be sure to get all #includes and replaced
filename, conditional includes through the whole hierarchy of include
statements - that would be too much.

Regards
Stephan


.

Relevant Pages

  • Re: Convert active characters into control sequences
    ... > I still do not perfectly perceive how to put your suggestion ... A final alternative is to use a preprocessor. ... This creates a 3 character control sequence, ...
    (comp.text.tex)
  • Re: Conditional code
    ... I was wondering what on earth you were talking about until I looked ... > closely at my earlier suggestion .. ... This might work with some compilers, ... assume that preprocessor doesn't generate any new comments. ...
    (comp.lang.cpp)
  • Re: "typedef" in F95/2003?
    ... Ken Fairfield wrote: ... so your suggestion has no effect on the ... My choice is still a preprocessor, ...
    (comp.lang.fortran)
  • Re: Need - macros feature
    ... but my question was about MACRO option, so the preprocessor should work ... and produce ruby source ... Farrel's suggestion (metaprogramming with attr_accessor) is the right one. ...
    (comp.lang.ruby)