From: Jurko GospodnetiÄ (jurko.gospodnetic_at_[hidden])
Date: 2008-01-09 06:34:54
> PS. I also reverted some of the white space, and style changes. Such
> changes make it much harder to follow the relevant history of the bjam
> code. Which given how depressingly hard it already is to follow that C
> code, I'd rather reduce the obfuscation of the change history.
Ok. Btw. does this 'no-touchy' rule hold only for bjam C sources or
for other Boost Build/Jam code as well?
IMHO it is better practice to nibble at complicated code, make it
cleaner piece by piece, then to say 'this is too complicated, do not
touch it if it ain't broken'. Makes the code much less fragile in the
end and eventually even removes/reduces the complication.
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