I am aware of this issue and its solution. I not convinced that this solution doesn't have some detrimental side effects or whether it will create some very difficult to find problem. That's where it stands now. Robert Ramey Vincent Agnus wrote:
Hi, robert
Thank you for your answer. My application is mono thread and duplicated code for seralization is granted to be the same. Our code actually forbide this design. What about replacing line 74&75 of
extended_type_info.cpp : 74 assert(lookup(eti) == m_self->m_map.end()); 75 m_self->m_map.insert(eti);
by
if ( lookup(eti) == m_self->m_map.end() ) { m_self->m_map.insert(eti); }
? With this new behavior the same type_info can be registred several time.
With this modification my design work fine. I can send you a sample of code if you want to investigate the problem
Best regards,
Vincent Agnus
Robert Ramey wrote:
There are two issues with the serialization library
a) Its not currently thread safe b) Serialization code can be duplicated in different shared libraries. It's not clear what this implies.
The first is on a path to final solution. It will depend upon the existence a thread-safe lazily initialized singleton which will have to be provided by the user until boost has such a thing (if that ever happens).
I'm still thinking about the second. What it means and the best way to address it.
Robert Ramey
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users