Re: [Boost-users] serialization 1.36.0 extended_type_info exit issue(s)

8 Oct 2008

      I don't understand why the extended type info should be static/global.

Why not provide something like:

namespace boost
{
  class extended_type_info_storage;
  shared_ptr<extended_type_info_storage> serialization_init();
}

We can require that this function is called prior to any other
serialization library function, and that the
extended_type_info_storage object is afloat while the serialization
library is in use.

If the user wants to make the returned shared_ptr a static/global
object (and deal with all the problems being discussed in this thread)
they can certainly do so -- but we won't have to support them.

Emil Dotchevski
Reverge Studios, Inc.
http://www.revergestudios.com/reblog/index.php?n=ReCode