🚀 go-pugleaf

In "The Standard C++ Library" on page 65, Plauger wrote:

  "I strongly encourage you to follow the lead of the Standard C++
   library in the use of exceptions:
   * Throw only objects of one or more classes derived from [exception]

Page 19-1 of the 4/95 version of the draft says "The Standard C++
library provides classes to be used to report errors in C++ programs."

But in section 19.1.1 of the same draft it says:

"The class exception defines the base class for the  types  of  objects
 thrown  as  exceptions by *C++ Standard library components*, and certain
 expressions, to report errors detected during program execution."

Can someone on the committee indicate whether it was the committee's
intention for the standard exception class hierarchy to be used in
general C++ programming, or whether the intention was for the standard
exception class hierarchy to be reserved to the Standard C++ library?

Another developer on our team has asked
  How can we be sure that ANSI C++ library callbacks work
  correctly in the face of exceptions?  What if ANSI C++
  library code catches *our* exception?

Is this a problem, or are library functions required to reraise any
exceptions thrown by client code? 

Kevin Cline
---
[ comp.std.c++ is moderated.  To submit articles: try just posting with      ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu         ]
[ FAQ:      http://reality.sgi.com/employees/austern_mti/std-c++/faq.html    ]
[ Policy:   http://reality.sgi.com/employees/austern_mti/std-c++/policy.html ]
[ Comments? mailto:std-c++-request@ncar.ucar.edu                             ]