Re: Exception specifications unfortunate, and what about their future?

Suppose you were to write a standard-style container, i.e. a container
with copy semantics that is able to hold any type. Let's just look at a
simplified implementation of insert:

template <typename T> class my_container
{
   //...

   iterator insert(iterator pos, T const& item) throw (my_exception)
   {
      iterator new_pos = make_room(1);

      try
      {
         *new_pos = item;
      }
      catch(...) // T might throw anything
      {
         // what goes here?
      }

      return new_pos;
   }

   //...
};

How could generic code possibly translate an exception that is specific
to T's problem domain into a generic format, and even if it could, how
could it avoid losing information? There's T-dom code on top which
understands and handles T-dom exceptions, and T-dom code at the bottom
which generates T-dom exceptions. You suggest that T-dom abandons its
specific exceptions although they make perfect sense, just because the
generic container is used in between. I don't see any sense in that.