Subject: Re: [boost] Failures for GCC 4.4.1 with gnu++0x
From: Beman Dawes (bdawes_at_[hidden])
Date: 2009-09-05 12:59:37
On Sat, Sep 5, 2009 at 12:47 PM, Beman Dawes<bdawes_at_[hidden]> wrote:
> What about a macro "#define nullptr 0" that is only defined if the
> compiler does not support C++0x nullptr? It usually is a really bad
> idea to give a macro a lowercase name, but isn't this a really special
> case because nullptr is a C++0x keyword?
Never mind. It would break existing code. Google code search shows
people already using the name, presumably in workarounds in
preparation for 0x.