This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Porting Questions
- To: Phil Edwards <pedwards at disaster dot jaj dot com>
- Subject: Re: Porting Questions
- From: Gabriel Dos Reis <Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr>
- Date: 28 Jun 2001 00:53:02 +0200
- Cc: "David A. Greene" <greened at eecs dot umich dot edu>, libstdc++ <libstdc++ at gcc dot gnu dot org>
- Organization: CMLA, ENS Cachan -- CNRS UMR 8536 (France)
- References: <3B3A29C2.7090401@eecs.umich.edu> <20010627152848.A12289@disaster.jaj.com>
Phil Edwards <pedwards@disaster.jaj.com> writes:
| Rather than additional macros, I'd recommend leaving the builtins spelled
| as they are
That is certainly my opinion.
| Good, since (void*)0 is an invalid definition for NULL. I hope we're not
| doing that anywhere in libstdc++.
GCC as a magic treatment for NULL.
| GCC defines a magic __null for precisely these reasons... there's an example
| of how to define a magic NULL in userland on the libstdc++ website, but
| it needs an empty default ctor added.
I won't recommand that solution.
| Can't help you there, unfortunately. After the discussion involving
| definitions, specializations, instantiations, and AIX freaky-weirdness,
| my understanding of templates has regressed. I don't think I understand
| them anymore. :-)
It is basically a non friendly linker issue. But the discussion was
confused because of some misunderstanding about C++ notions.
-- Gaby