David Abrahams <davi...@rcn.com>
There is quite a lively discussion going on on the scons development list at
sourceforge about this very issue. Cons (and scons) uses an innovative
scheme for cacheing dependency information that I find quite compelling. I
am beginning to think we should just build this mechanism into the
underlying Jam engine. I need to look at it a bit more carefully, but it
seems like it could solve lots of problems.
Could you describe it?
While reading mail makes for a nice change from forcing a huge chunk of
broken source code to compile on a similarly broken beta-quality and
overhyped CPU (<- letting off steam), I don't particularly want to
subscribe to another mailing list.
--Arnt