Boost C++ Libraries: Ticket #2096: program_options fails to compile with -fno-exceptions

attachment set

anonymous — Thu, 10 Jul 2008 04:14:49 GMT

attachment → boost_program_options_no_exceptions.diff

Vladimir Prus — Thu, 10 Jul 2008 07:39:52 GMT

With BOOST_NO_EXCEPTION, you're supposed to provide your own definition of throw_exception. Can you tell what that definition will do? Whereas aborting if an error happens during option parsing seems possible, I'm not sure what you might do on an error during getting an option.

brbarret@… — Thu, 10 Jul 2008 13:42:28 GMT

Yeah, that's a really good question. To be honest, I don't plan on using program_options in my application.

It is used somewhere in the default build of boost 1.35.0 (I have a hard time telling what exactly is being compiled when using bjam and didn't keep good notes on the subject, so I'm not sure whether it was in one of the libraries or the test cases. I'd assume the test cases, given what program_options does). The patch was mainly doing enough so that make all install would succeed when -fno-exceptions is used.

Vladimir Prus — Thu, 10 Jul 2008 14:10:16 GMT

Hmm, if you don't have first-hand experience that program_options is remotely useful with -fno-exceptions, then I suggest you just add "--without-program_options" to bjam, and skip the build.

status changed; resolution set

Vladimir Prus — Sun, 07 Jun 2009 16:10:04 GMT

status new → closed
resolution → fixed

(In [53723]) Make program_options compile with disabled exceptions.

It appears the all throw statements are during the parsing, so alternative error reporting strategies are possible. Closes #2096.