Re: Exceptions vs. undefined behaviour

From:

Pete Becker <pete@versatilecoding.com>

Newsgroups:

comp.lang.c++.moderated

Date:

Tue, 6 May 2008 12:45:04 CST

Message-ID:

<2008050610143516807-pete@versatilecodingcom>

On 2008-05-06 04:43:26 -0400, Johan Torp <johan.torp@gmail.com> said:

IIRC, the standard library avoids throwing exceptions so that users
which compile without exception support shall be able to use as much
of the standard library as possible. Is this correct,

No. The standard library is specified for the standard language.

incorrect or are
there other motivations?

Will this also be the case for the newly accepted libraries and for
TR2?

Will this "undefined behaviour"-strategy only apply to broken pre-
conditions or will error codes and the like be used for reporting
internal errors?

The standard library doesn't "avoid throwing exceptions". In general,
the design is to throw exceptions when they're appropriat, and not
throw exceptions when they aren't. Most cases of undefined behavior
occur because the violation of the rule can't easily be detected.

--
  Pete
Roundhouse Consulting, Ltd. (www.versatilecoding.com) Author of "The
Standard C++ Library Extensions: a Tutorial and Reference
(www.petebecker.com/tr1book)

      [ See http://www.gotw.ca/resources/clcm.htm for info about ]
      [ comp.lang.c++.moderated. First time posters: Do this! ]