Re: [Boost-bugs] [Boost C++ Libraries] #7971: [C++11] Boost::Format doesn't like to be fed nullptr/std::nullptr_t

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #7971: [C++11] Boost::Format doesn't like to be fed nullptr/std::nullptr_t
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2017-10-13 18:40:48


#7971: [C++11] Boost::Format doesn't like to be fed nullptr/std::nullptr_t
-------------------------------------+--------------------------------
  Reporter: Roger Leigh <rleigh@…> | Owner: James E. King, III
      Type: Bugs | Status: closed
 Milestone: Boost 1.66.0 | Component: format
   Version: Boost 1.50.0 | Severity: Problem
Resolution: wontfix | Keywords:
-------------------------------------+--------------------------------
Changes (by James E. King, III):

 * status: assigned => closed
 * resolution: => wontfix
 * milestone: To Be Determined => Boost 1.66.0

Comment:

 On further review, this is a C++ standards issue and not a Boost.Format
 concern.

 See:

 http://cplusplus.github.io/LWG/lwg-defects.html#2221

 A workaround is to define your own std::ostream operator for your program
 to work with a nullptr - it is not the responsibility of Boost.Format to
 do this for a native type. Doing so would lead to compatibility issues
 later if the standard changes requiring libraries to implement it - it
 would become ambiguous again.

 Additional discussion can be found on stack overflow which has suggestions
 for a workaround:

 https://stackoverflow.com/questions/31164961/operator-stream-output-for-
 nullptr

-- 
Ticket URL: <https://svn.boost.org/trac10/boost/ticket/7971#comment:3>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-10-13 18:49:05 UTC