On Thu, 12 May 2016, Dave Close wrote:
I am astounded by the number of non-bash scripts I've read that are nothing more than feel-good wrappers around a set of system() calls to get real work done. If you're using a scripting language because it enables you to write a "program" rather than just a series of calls, then /write/ a program. Otherwise stick to bash.
I had a case where a (ugly) 20 line shell script wasn't considered good enough for production use, so it was handed over to the engineering department to make 'production ready'.
What came back (a couple months later) was a 200 line script with many functions (all with severa lines of comments), which loaded the variable $command with parts of my original script and then made system() calls.
But it was deemed 'supportable' for mission critical use :-/ David Lang _______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
