Re: C++ keywords in headers (was Re: [GENERAL] #include ) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: C++ keywords in headers (was Re: [GENERAL] #include )
Date
Msg-id 17661.1293472202@sss.pgh.pa.us
Whole thread Raw
In response to Re: C++ keywords in headers (was Re: [GENERAL] #include )  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: C++ keywords in headers (was Re: [GENERAL] #include )  (Magnus Hagander <magnus@hagander.net>)
Re: C++ keywords in headers (was Re: [GENERAL] #include )  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Excerpts from Tom Lane's message of lun dic 27 13:54:56 -0300 2010:
>> [ lightbulb ] ... although we could improve that quite a bit if we
>> processed each .h file separately instead of insisting on smashing
>> everything into one compilation.  Let me go try that.

> FWIW I have this patch lingering about that I wrote months ago, to check
> for header problems (not C++ stuff, just things like forgetting to
> include some necessary header in some other header).  Since it needs a
> lot of polish (needs to ignore certain headers, and avoid leave
> lingering files around), I didn't commit it; and I haven't updated it to
> the new Make recursive stuff, either.

src/tools/pginclude/ already contains several scripts for this sort of
thing.  Bruce runs them by hand occasionally, although I just found out
that he's evidently not run the does-each-header-compile-standalone
test in awhile.  It would probably pay to automate these.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: C++ keywords in headers (was Re: [GENERAL] #include )
Next
From: Magnus Hagander
Date:
Subject: Re: C++ keywords in headers (was Re: [GENERAL] #include )