Re: [boost] Safety over efficiency guideline

From: David Abrahams (abrahams_at_[hidden])
Date: 2000-06-10 22:30:52

The counterargument to this is that programmers should never feel a nagging
doubt about adding an assertion, for fear that it will slow down the
shipping code.

-Dave
----- Original Message -----
From: "Branko Èibej" <branko.cibej_at_[hidden]>

And a good example of how things _shouldn't_ be done is the Microsoft
practice of not providing support for assert() in the optimized version
of their runtime library. Which means I can't use the faster library
and still keep assert()s in my code, although in my opinion an abort()
is always better than a segfault (or worse). Which in turn means that I
have to implement my own assertion macro; then what's the point of having
a standard interface?