Re:The Awk Programming Language (1988) [pdf]
by michaelfeathers on Sunday January 22, 2017 @10:57AM
(#13455678)
> I've always thought that AWK's most important feature is its self limiting nature
I agree. This idea doesn't receive enough attention. If you pick your constraints you can make a particular envelope of uses easy and ones you don't care about hard.
AWK's choice to be a per line processor, with optional sections for processing before all lines and after all lines is self-limiting but it defines a useful envelope of use.
Re:The Awk Programming Language (1988) [pdf]
by ams6110 on Saturday January 21, 2017 @11:39PM
(#13453608)
I've written one or two awk programs that probably went beyond what the tool was intended for, but mostly I use short one-liners or small scripts. I use awk, grep, sed, and xargs pretty much daily for all kinds of ad-hoc automation.
Re:The Awk Programming Language (1988) [pdf]
by joepvd on Sunday January 22, 2017 @05:41AM
(#13454597)
> beyond what the tool was intended for
Not sure what that would mean. I think the tool was designed to be a user's programming language. I liken to think that `awk` was the Excel + VBScript of its days.
Re:The Awk Programming Language (1988) [pdf]
by throwaway7645 on Sunday January 22, 2017 @09:46AM
(#13455350)
VBScript was largely replaced on Windows by Powershell. Awk is still popular for what it's good at.
Re:The Awk Programming Language (1988) [pdf]
by ams6110 on Sunday January 22, 2017 @10:22AM
(#13455491)
Fair point. I guess I meant more what I thought it was intended for, i.e. mainly smallish text transforms where the entire program is given on the command line, often as part of a pipeline of several different utilities.
But no, there's always one. :-)