From: John Maddock (jm_at_[hidden])
Date: 2002-11-02 05:49:35
> Ugh, now I see what's happening (roughly). It's the monstrosity
> below. Aside from being hideous, unmaintainable, and slowing the whole
> build process, is there some reason to ad this to the Jamfile? Is
> there a reason that these type_traits tests which all use identical
> boilerplate could not use some custom rules to eliminate code
> Sorry to be so arch, but if the boost test Jamfiles spin out of
> control it's going to make maintenance difficult for everybody...
Don't apologise, as you will have noticed the type_traits tests are in a
state of flux right now, they will settle down soon (honestly), and yes that
build everything test will be removed from status/Jamfile, it will stay in
libs/type_traits/test/Jamfile though as it is sometimes useful to build and
check everything at once with the more conforming compilers.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk