This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [C++0x] nullptr
- From: Ed Smith-Rowland <3dw4rd at verizon dot net>
- To: Magnus Fromreide <magfr at lysator dot liu dot se>
- Cc: Jason Merrill <jason at redhat dot com>, gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Date: Mon, 03 May 2010 01:05:00 -0400
- Subject: Re: [C++0x] nullptr
- References: <1268546192.2028.32.camel@sara.home> <4BA46E77.6080507@redhat.com> <1269813166.2249.8.camel@sara.home> <4BB12B74.80703@redhat.com> <4BDD0915.2020301@redhat.com> <1272842221.2000.26.camel@sara.home>
Greetings,
I tried to do nullptr and I'm gratified that some of what I tried you
did too ;-).
It was a learning experience as I had never touched the front end before.
Anyway, my question is this:
In gcc we
#define NULL __null.
OTOH the committee thought about and ultimately rejected
#define NULL nullptr
Can/should we go ahead and do this since we sort of did it already?
If we don't want to do this would it be a good idea to have a flag
-fNULL=nullptr o somesuch?
Thanks,
Ed