Boost Users :
Subject: Re: [Boost-users] serialization 1.36.0 extended_type_info exit issue(s)
From: Emil Dotchevski (emil_at_[hidden])
Date: 2008-10-08 14:07:17
I don't understand why the extended type info should be static/global.
Why not provide something like:
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.
Reverge Studios, Inc.
Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net