Paul Eggert wrote: > My biggest worry wasn't confusion, but compilers that complain about > "#include_next" even in code that is ifdeffed out. The C standard > says such programs are OK but I vaguely recall some compilers from > decades ago that complained about such things.
Yes, the IRIX 6.5 compiler gives a warning about #include_next, even inside #if 0: "foo.c", line 2: warning(1011): unrecognized preprocessing directive #include_next <stdlib.h> ^ If we want to work around it, it's easy: have a substitution @INCLUDE_NEXT@ that expands to #include_next or to empty... Bruno
