On Mon, Feb 14, 2022 at 7:46 AM Peter Dimov via Boost
Vinnie Falco wrote:
On Sun, Feb 13, 2022 at 1:44 PM Peter Dimov via Boost
wrote: Recommendation one: add source_location default arguments to your throwing functions so that the information logged at the catch site points to the call that threw.
I am less excited about changing the signatures of all public
functions. I
thought that BOOST_THROW_EXCEPTION attached a stack trace to the exception?
No, it doesn't attach a stack trace.
No, it attached the throw location in a different way. The plan is to expose the new source_location type through the same get_error_info interface that is used to access the legacy boost::throw_function, boost::throw_file and boost::throw_line. Also, we should continue to provide this information the "old" way, so that old code can read the source_location.