From: Joe Gottman (jgottman_at_[hidden])
Date: 2007-08-07 19:42:53
Stefan Seefeld wrote:
> Beman Dawes wrote:
>> A draft "Development and Release Practices" document is up on the Wiki:
>> Comments welcomed!
> Overall this sounds good. The one thing I'm not sure about is the introduced
> dichotomy between core and non-core libraries. Why not simply talk about
> prerequisite libraries as those libraries others depend on ?
> This reuses the technical term 'prerequisite', and doesn't overload the meaning
> of 'core'. In other words, whether or not a library belongs into the 'core' (whatever
> that is), and whether it is a prerequisite for another library, are two distinct and
> orthogonal questions.
One problem I can see is that just about everything is a prerequisite
of the serialization library. Not only does it depend on a lot of other
classes, but changes to the other classes that would not break most
clients will break the serialization code: for example if a class adds a
new data member and a constructor with an extra parameter to initialize
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk