ambiguity in c99

[Kuciwalker]

cpp doesn't like this very much:

foo_p.h:

#ifdef FOO

foo.h:

#include "foo_p.h"
#error
#include "foo_e.h"

foo_e.h:

#endif

I read through the 2007 revision of the C99 standard and it doesn't comment on this usage, but a natural reading would imply that it should be correct. However, cpp, even with -std="c99", does not approve.

Does anyone have a definite answer whether this is/is not correct?

edit: I'm aware that wanting to do something like this makes me a bad person. I don't care.

[Asher]

It's my understanding that the #if/#endif scope was file-specific for the preprocessor.

It might not be specifically mentioned, but it was probably too obvious to mention.

[Kuciwalker]

[Asher]

The C/C++ Standards, at least circa 2004, were wonderfully ambiguous in many areas.

[Provost Harrison]

Are you calling PH a foo?

[Tuberski]

Tech foorum....

ACK!