[travisgriggs]

Years ago, I had inherited a complicated C code base with some clever Makefile jujitsu. None of the recent maintainers understood it at its core. They just put a little lipstick here, and a little there to keep things running.

I sat down and extracted the compiler/link flags, and then wrote a Python script to do the build. The code was smaller, and built faster.

Every “build” engine evolves from being a simple recipe processor to the software equivalent of a 5 axis CnC mill. Some things should not succumb to one size fits all.

[ngcc_hk]

Python is good enough.

Maintainability? Just if one start any OO features, one will gradually deal with modern day goto scenario. One can start another round of guessing, especially you have global.

I found it is easier to read a lisp or a c (functional mostly) source than python. But guess we have to use python these days.

Btw, your saying sound like the usual lisp meme - for every … there is a tiny untested lisp engine there.

[intelVISA]

> Every “build” engine evolves from being a simple recipe processor

what if I told you it was every machine