1 Jan
2013
1 Jan
'13
10:49 p.m.
Daniel James wrote:
On 19 December 2012 04:47, Eric Niebler <eric@boostpro.com> wrote:
Regardless, (speaking as a release manager) I'd like to see this addressed one way or the other since it's a breaking change.
What's the way forward?
Assuming that we want to support this configuration, the options I see are - Config defining std::nullptr_t as it does with size_t; - Config defining BOOST_NO_NULLPTR_T, so that libraries can activate workarounds, or - SmartPtr fixing the problem somehow without Config involvement, which would entail detecting the problematic configuration in some way.