Re: #ifdef __cplusplus

Ian Collins said:

> Richard Heathfield wrote:
>> Ian Collins said:
>> 
>>> Richard Heathfield wrote:
>> <snip>
<crunch>
>>>> #ifndef H_CPP_FOO/#define H_CPP_FOO 1/extern "C"
>>>> {/#include "foo.h"/};/#endif
</crunch>
>>>>
>>>> and then #include "cppfoo" in the C++ code.
>>>>
>>> As I said elsethread, this woks in isolation but craps out of foo.h
>>> includes a header with its own wrapper.
>> 
>> But why should it? foo.h is a C header! If it includes a "header with
>> its own wrapper", it's breaking the model. Being a C header, it should
>> only include other C headers.
>> 
> C standard library headers are also C++ standard library headers.

Standard library headers can (ab)use the "as-if" rule to do what they like

as long as it all works. I was under the impression that we were 
discussing non-implementation headers.

-- 
Richard Heathfield <http://www.cpax.org.uk>
Email: -http://www.
+rjh@[EMAIL PROTECTED]
 users: <http://www.cpax.org.uk/prg/writings/googly.php>
"Usenet is a strange place" - dmr 29 July 1999