Sohail Somani wrote:
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Emil Dotchevski
Not to mention that the client can and will do it wrong.
I don't want to make a huge deal out of this because ultimately I don't mind hiding the dynamic_cast in a function get_exception_info. But I am arguing that this abstraction is not necessary because the only implementation possible is through a dynamic_cast (at least I can't think of another possibility).
Well for some people the only way to fix a const correctness related error is to remove the const. I can imagine people doing all sorts of (wrong)casts. IMHO, I think the api should constrain that freedom seeing as there *is* only one right way to do it!
Please let's keep this to the point. There are no const_casts in the proposed Boost Exception library. If you think that the dynamic_cast can be avoided, I'm very much interested to hear how. If you think the need for dynamic_cast is a result of poor library design, I'm very much interested to hear about any improvement ideas. --Emil