This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC headers and DJGPP port
In article <200007201205.OAA15361@loewis.home.cs.tu-berlin.de> you write:
>> > I had hoped you could have concluded that it either does or
>> > does not break the library.
>> We couldn't do that because we had no information on how __null works
>> in the C++ compiler. If we missed something in the docs, please tell
>> where we should have read about it.
>It is not in the texinfo documentation, as it is not intended to be
>used by anybody then the "implementation" itself (which consists of
>the compiler, and the standard library). There is a note in cp/NEWS
>you may not have seen, though.
This is wrong.
Quoting from the documentation:
This manual documents how to run, install and port the GNU compiler,
as well as its new features and incompatibilities, and how to report
bugs. It corresponds to GCC version 2.96.
There *is* a place in the documentation for this kind of details.
Knowing about __null and what it entails may be very useful when
porting gcc to a new architecture, or making it work in system-specific
implementations, where you tend to muck with --nostdinc and other such
switches.