From: Tom Bachmann (e_mc_h2_at_[hidden])
Date: 2007-03-19 09:49:55
-----BEGIN PGP SIGNED MESSAGE-----
>> Wouldn't it make sense to move that to a separate "official" location,
>> say, the toplevel boost namespace? Afterall, it is nothing specific to
>> python, and I cannot understand why it should be in boost::detail. Am
>> I missing something?
> I assume because no one needed it as a separate library previously? There is
> also an extended type info class as a detail of the serialization library
> that you might look at as well.
I strongly dislike the idea of using something declared in
boost::detail, or anything that's not part of the official interface. Do
others experiece a need to move one of the type_info wrappers to some
official location? That there are multiple more or less equivalent
classes for that purpose even in boost seems to indicate to me that it's
use is not so remote, and having duplicated functionality doesn't sound
that good either.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
-----END PGP SIGNATURE-----
Boost list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk