> 3) Security features for distributed systems ... sh is obviously not > designed for untrusted input (including what's on the file system).
4) ... along these same lines, a lot of other people are annoyed by the gratuitous and crippled shell in make: https://github.com/apenwarr/redo -- implementation of a DJB design, each rule is a shell file, so you automatically get the property that changing the command line/rule invalidates the output, which Make doesn't have) https://github.com/danfuzz/blur -- from the author of the Android.mk system (which slurps a big tree Make fragments into a single namespaced Makefile). I guess he got sick of Makefiles after that ... Both of these have issues but are interesting... I think it wouldn't be too hard to make a shell in which you could IMPLEMENT make. It seems like you've gone a little in that direction with your "isnewer" checks in scripts/make.sh! The problem is that all this stuff is at the foundational layer, and being backward compatible with both shell AND make is a very tall order (although I guess that's where my interests overlap with toybox) Andy _______________________________________________ Toybox mailing list [email protected] http://lists.landley.net/listinfo.cgi/toybox-landley.net
