🚀 go-pugleaf

In <4du1v6$h74@jupiter.SJSU.EDU>, horstman@jupiter.SJSU.EDU
(Cay S. Horstmann) writes:

>I am not sure exceptions are the way to go--the great value of a
>standard is that it is, well, standard. STL may not be the greatest
>library on the planet, but it is certainly good enough, and it is
>standard. I don't like the idea of tinkering with the interface by
>adding exceptions.

OK, but what about guarantees on the behaviour of a container when, 
say, the constructor of a contained object throws an exception?  Can
anything then be said about the state of the container?  Can the 
container itself (with, perhaps, other contained elements) be restored
to service?  Can it even be cleaned up, or will unrecoverable memory
or other resources be left behind?

I think this is a hard problem.
----
Jim McElroy
Bellevue, Washington
---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]