On 1 January 2013 22:49, Peter Dimov <lists@pdimov.com> wrote:
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
I was asking more about how (or perhaps, who) to get started on a fix/workaround.
- Config defining std::nullptr_t as it does with size_t; - Config defining BOOST_NO_NULLPTR_T, so that libraries can activate workarounds, or
If you want to add something to config, it might be a good idea to write that in a post with [config] in the subject line, or to open a ticket. Although I prefer Eric's boost::nullptr_t, adding things to 'std' is a bad idea, precedents notwithstanding.