Re: AWK As A Major Systems Programming Language

Stefan Ram <ram@zedat.fu-berlin.de> wrote:

ram@zedat.fu-berlin.de (Stefan Ram) wrote or quoted:

Trying to make that Python script more user-friendly for folks
who dig awk, then rolling out a sleeker version . . .

 
 The setup with a class and a bunch of named functions had some perks,
 though: The class and function names are like a cheat sheet, spilling
 the beans on what the coder was up to. They keep things chill by
 breaking up the work, each one zeroing in on just one part of the gig.
 Plus, they give you a solid jumping-off point for unit tests.

I see your point. Depends on what you're trying to read too really
- what the script's author is trying to achieve, or what exactly
the script does. To achieve the latter there's more to parse in the
first version in order to see what's actually happening, and that's
what I was comparing to the AWK version.

--
__          __
#_ < |\| |< _#