Re: Probably a 3.2.5 fix coming

Roger Leigh <[email protected]> writes:
 
> nullptr is a language keyword, so that should just have worked.  Unless
> an older language standard was being explicitly forced, the use of
> nullptr should be benign.

nullptr was added in C++11 so by using it you effectively drop
support for C++98/03. I personally don't mind dropping this
support but I think it should be a bit more formal than "ops, 
we just dropped C++98/03 accidentally". I.e., a vote and a
note in the release notes would be a good idea.