One of the benefits of making this library part of Boost is that people working on different OSes will be able to add custom, OS-specific information in a Boost Exception at the time of the throw. A stack dump, captured in the boost::exception's constructor, would definitely be very helpful. Emil Dotchevski On 9/30/07, Oliver.Kowalke@qimonda.com <Oliver.Kowalke@qimonda.com> wrote:
Did you see my earlier answer to your question? Here's a link in case you've missed it:
Yes - some emails are missing :^(
http://article.gmane.org/gmane.comp.lib.boost.devel/165486/mat ch=boost%5ferror%5finfo
I'm using boost.exception in a project and I think such a stack could be helpful in case of errors/exceptions. For instance in an layers application and a lower layer throws an exception - the stack can help to identify the parts of the related layers (because the code of the lower layer could be called from different code segments in the upper layers).
Oliver _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost