I see that this has been the topic of much discussion lately, but just
confirming this little warning from the regressions has not snuck by
unnoticed:
# 'boost::bad_lexical_cast::what()' hides inherited virtual function
'std::exception::what() const'
[const missing, to state the obvious
From: Alisdair Meredith [EMAIL PROTECTED]
I see that this has been the topic of much discussion lately, but just
confirming this little warning from the regressions has not snuck by
unnoticed:
# 'boost::bad_lexical_cast::what()' hides inherited virtual function
'std::exception::what() const
You might want to read
http://www.objectmentor.com/resources/articles/lsp.pdf for
a rationale of the LSP. A somewhat different view is expressed in
http://alistair.cockburn.us/crystal/articles/cdos/constructivedesconstructionofsubtyping.htm.
Am Son, 2003-03-23 um 14.00 schrieb David Abrahams:
Yes. Since type_info objects can't be copied, one might instead store
pointers or references to them.
Pointers would be better because, for better or for worse (mostly for
worse), standard exceptions support assignment as part of their
interface.
Why should boost exception classes behave
