Ah - I stand [partially] corrected... * Never write it in perl if you can do it in `bash'.
However, depending on how involved the script ends up, it could end up shorter and easier in perl. OTOH, modern bash is much easier to write in than the bourne I used "way back when" - I used bourne sh when I "should" have used perl. If it had been available. Functions and aliases can help make bash much more like a "real language". --Don Ellis On Tue, Feb 10, 2009 at 3:17 PM, Robert Citek <[email protected]>wrote: > > On Tue, Feb 10, 2009 at 2:49 PM, Don Ellis <[email protected]> wrote: > > Sweet! I like that one (other than that it's in bash instead of perl) ;-) > > --Don Ellis > > Substitute perl for C and bash for awk. > > Taylor's Laws of Programming > > * Never write it in C if you can do it in `awk'. > * Never do it in `awk' if `sed' can handle it. > * Never use `sed' when `tr' can do the job. > * Never invoke `tr' when `cat' is sufficient. > * Avoid using `cat' whenever possible. > > And like all clever phrases, take with a grain of salt. :) > > Regards, > - Robert --~--~---------~--~----~------------~-------~--~----~ Central West End Linux Users Group (via Google Groups) Main page: http://www.cwelug.org To post: [email protected] To subscribe: [email protected] To unsubscribe: [email protected] More options: http://groups.google.com/group/cwelug -~----------~----~----~----~------~----~------~--~---
