|
Boost : |
From: Pavel Vozenilek (pavel_vozenilek_at_[hidden])
Date: 2004-04-25 12:29:39
"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.
> 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 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>.
Maybe name boost/date_time/gregorian/serialization/... would fit better.
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.
/Pavel
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk