From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-05-14 01:52:23
We were discussing this issue with Dave and I think we've reached a
conclusion. But I'd like to make sure we all agree to it. The proposal is for
a simple rule
All non-trivial changes to Bjam core must come together with tests.
Does everyone agree?
The motivation is that jam/bjam itself is not very good tested, and if we
continue adding untested features, bjam will only degrade. The more direct
issue is that recently, typechecking facilities were added to bjam, and I did
not seeing the exact description of semantics, or any tests. As result, I had
to look up in code to understand how it works. A simple tests (which I
already comitted) would be sufficient to understand everything.
(There's some test in class.jam, actually, but it's not executed by default
and is too high-level to understand how new feature works).
Boost-Build 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