Re: What risk of undefined behavior if destructor must throw?
Gennaro Prota wrote:
On 12 Oct 2006 09:54:30 -0400, "kanze" <kanze@gabi-soft.fr> wrote:
Gennaro Prota wrote:
Absolutely! On a related issue: do you use the standard
assert macro for that (thus taking care of not defining
NDEBUG even in "release" builds) or do you have your own
assert facility?
It depends. For in house software, such I currently work on,
the standard assert facility is fine. For software which is
meant to be used out of house, I generally prefer my own
asserts, in order to ensure that the error message contains
enough information so that the user knows it is an internal
error, and knows to contact support.
I see. My question was more about the technical aspect though;
I find the standard assert macro too prone to ODR violations
and linking issues.
Such as? About the only one I can think of is if you compile
some modules with NDEBUG defined, and others without, and even
then, it would only affect inline functions and non-exported
templates, and in practice, will work anyway. And of course, in
the twenty-five years I've been doing C/C++, I've never compiled
a module with NDEBUG defined, so the problem doesn't exist
anyway.
So I wondered if you just used something like const bool
debug_on = ... (in lieu of NDEBUG) or a more sophisticated
solution :-)
For pure assertions, no. I use something similar for logging,
and it's true that in some applications, logging an error
message with a fatal log precedance is preferred. It all
depends on who is using the application: if the application only
runs on a few systems, with (presumably) competent
administrators, and the absence of the application will be
immediately noticed, assert is fine. If there's normally no one
watching the machine, on the other hand, I'll generally use the
logging mechanisms to ensure that the message gets sent to
syslog or a responsible's email, rather than appearing on a
std::cerr connected to /dev/null.
--
James Kanze GABI Software
Conseils en informatique orient?e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S?mard, 78210 St.-Cyr-l'?cole, France, +33 (0)1 30 23 00 34
--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]