Re: [Boost-bugs] [Boost C++ Libraries] #11888: boost.test throws an exception when passed a custom command line parameter

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #11888: boost.test throws an exception when passed a custom command line parameter
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2016-01-11 15:37:33

#11888: boost.test throws an exception when passed a custom command line parameter
-------------------------------------+-------------------------------------
  Reporter:  James Whitworth         |      Owner:  renficiaud
  <fun4jimmy@…>                      |     Status:  assigned
      Type:  Bugs                    |  Component:  test
 Milestone:  To Be Determined        |   Severity:  Showstopper
   Version:  Boost 1.60.0            |   Keywords:
Resolution:                          |  test;runtime_config;commandline;
-------------------------------------+-------------------------------------

Comment (by James Whitworth <fun4jimmy@…>):

 I think having the api in changes in '''change_log.html''' is the best
 place for them. I would have liked to know:
  - the call to `boost::unit_test::runtime_config::log_format()` was
 replaced with a generic template system
 `boost::unit_test::runtime_config::get<boost::unit_test::output_format>(
 boost::unit_test::runtime_config::OUTPUT_FORMAT)`, this could then link to
 the '''runtime_config.html''' page with a more detailed explanation
  - The enum for format types was renamed `boost::unit_test::XML` was
 renamed to `boost::unit_test::OF_XML` etc.
  - `boost::unit_test::unit_test_log_formatter::test_unit_skipped()` now
 takes a const_string reason.
  - `boost::unit_test::unit_test_log_formatter::log_exception()` was
 replaced with `log_exception_start` and `log_exception_finish`
  - `boost::unit_test::unit_test_log_formatter` has new functions added for
 contexts: `entry_context_start()`, `log_entry_context()` and
 `entry_context_finish()`

 If all that was available from the '''change_log.html''' then there would
 be less digging around in the source to see what was required to fix up.
 If any of these were marked as internal to boost test then I understand
 it's up to me to fix them but if they are in the public api then it would
 be good to have some mention of the changes.

 I guess doing a diff with the last released version would get you a good
 idea of what should be mentioned.

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