-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Emil Dotchevski

...

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.

You're missing my point. I didn't say that dynamic_cast in this way is bad, nor did I say someone would use const_cast. I was only pointing out that there are those who will just do what they can to get it to look like it works. Restrict those people. Sohail