Re: [boost] Re: [serialization+date_time] SerializationReview:serialization of dates

From: Jeff Garland (jeff_at_[hidden])
Date: 2004-04-25 13:16:21

On Sun, 25 Apr 2004 19:29:39 +0200, Pavel Vozenilek wrote
> "Jeff Garland" <jeff_at_[hidden]> writes
> 
> > > 'boost/serialization/boost' directoy could be used for all
> > > Boost libraries. One place is better than to have bits
> > > scattered accross source tree.
> >
> > Well, I think it belongs in the library supplying the data type not in
> > serialization.  Few reasons for this...
> > 1) I don't want serialization depending on every library in boost -- the
> other
> > way around makes more sense.
> >
> It is not that Serialization library would depend on others.
> It is just place to put headers.

Well, I guess since it is all templates the dependency isn't real strong but I
still don't like code for other libraries under the serialization tree.  Also,
 this approach prevents libraries from using non-template code -- although
maybe that doesn't matter since all the serialization intefaces are
templatized.  Perhaps pending the outcome of the polymorphic archive addition.

> > 3) If the developer chooses to add serialization internally in their class
> > then the code has to be in the client library.  I don't think we should
> force
> > boost developers to use the external serialization like I posted.
> >
> Yes.

So if most developers do this and few don't then we will have an uneven
solution for users.  Sometimes they will need to go to a path under
serialization and sometimes they won't.  I think always putting that code with
the client library makes more sense.  If it requires an additional header to
be included that should be documented in the downstream library.

> > So for the particular case I posted I was planning on putting this code in
> >  boost/date_time/gregorian/greg_serialize.hpp
> >
> > Time could would go into
> >  boost/date_time/posix_time/time_serialize.hpp
> >
> Current naming conventions are like:
>    boost/serialization/vector.hpp
> for <vector>.

Sure, but that's because boost doesn't have a way to change the standard
library headers.  If serialization was part of the standard I would expect to
get the ability to serialize just by including <vector>.  Of course there
would still be some other include like <archive> to get the archive headers. 

> Maybe name boost/date_time/gregorian/serialization/... would fit better.

I think having another directory level just for one serialize.hpp is a bit
much.  BTW, I forgot to say that I was assuming that 
  boost/date_time/gregorian/gregorian.hpp
  boost/date_time/posix_time/posix_time.hpp

which are the 'include everything' files for date_time will also include the
serialization code so that no extra work will be required for most users.

> Whatever, it should be easy for user to find of whether or not
> library supports serialization. Maybe some publicly editable page
> in docs is solution.

I was assuming I would need to introduce documentation in date_time that shows
all the serializeable types.  An example would also be nice.  I would also
like to see a table in the serialization docs that lists the boost libraries
that support serialization.  Probably just a simple table that points off to
docs in the other libraries.  I think the combination of these 2 things should
make it easy for users to find what is supported.

Jeff