Re: [boost] [serialization] extended_type_info as extensions/plugins library ?

9 Oct 2006

      Janek Kozicki wrote:
...
Think of it. With two separate libraries (one for serialization
and one for plugins) the user will have to register each class twice.
Serialization already registers classes with GUID (Global Unique
IDentifier) so plugins/extensions library should take advantage of
that.
Oh no.  registering a data type for export would be sufficient
for plug-ins AND serialization.

So I would like to see:

a) a plug-in library based on ehancement of extended_type_info
b) serialization tweaked to use this library.

The we get a "smaller" serialization library - and a separate
self contained library which is useful for other things.  Just
a little code re-factoring.

Robert Ramey