Hi Gennadiy, Am Montag, 5. Oktober 2015, 18:47:20 schrieb Gennadiy Rozental:
I tried to explain rationale here:
Gah, I overlooked that one, too. The rationale makes sense.
In a summary: we want to properly report incorrect command line arguments. This kind of scheme is used in many places and Boost.Test just follow the suite.
I'm with out at this. Maybe some more SHOUTING in the subject would have been better. And maybe some preprocessor #define to select old/new commandline parser during compilation. This would have allowed the testers to use the old behaviour while figuring out how to adapt testing.jam. The same goes for c++11/03 switches, of course. But I think that going forward is the best way out of this... Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold@gmx.eu ! Germany