GCC headers and DJGPP port

[Gabriel Dos Reis]

Jeffrey A Law <law@cygnus.com> writes:

[...]

| Let's take the __null issue again.  According to the C++ standard it is
| an implementation-defined C++ null pointer constant -- it also states
| that (void *)0 is not an acceptable value.
| 
| It turns out that using "0" doesn't work, nor does "0L" for reasons I
| can't remember.

"0" or "0L" might be acceptable, for an appropriate definition of
"acceptable".  However, I'm firmly convinced that GCC's approach is the
way to go, as far as the C++ front-end is concerned.  It enables us to
issue warning when a use of NULL might lead to unintended semantic.
In that regard, GCC is far superior to its competitors.

-- Gaby
CodeSourcery, LLC                             http://www.codesourcery.com