Mail Archives: djgpp-workers/2000/07/20/13:49:56
> Date: Thu, 20 Jul 2000 08:25:40 -0700
> From: Bruce Korb <bkorb AT sco DOT COM>
>
> The worst one *is* NULL. The reason is that there are so bloody
> many platforms out there that define it in all manner of random places.
> I assume you know that. GCC has to adapt itself to all these platforms.
Sorry, I don't see why does GCC need to adapt itself. Does this need
arise when building GCC, or when using it (or both)?
And what problems are caused by the fact that NULL is defined in many
places? Are you talking about platforms which don't have NULL defined
in the usual places, such as stddef.h? If so, I think the platforms
which do have NULL defined where it should be, should not be punished
on behalf of the non-conforming platforms.
> > Of course, a working fixincludes might circumvent the technical
> > problems.
>
> I'm ready to help, but I don't have a DOS platform to play on.
You don't need to have a DOS machine, any Windows 9X or NT machine, or
even Linux with DOSEmu, will do: DJGPP supports all these platforms.
You could even try this on Unix, if you only use Posix functions like
popen, system, and dup.
Please don't misunderstand me: I'm not saying that you *should* do
this yourself, I'm saying that you _can_ do this should you wish to.
- Raw text -