Many of you know that I\u2019m a big fan of AWK. After Lisp and C, it\u2019s my go to language, especially for scripts that involve reading a bunch of lines and performing some sort of regex-mediated action on them. Its language is basically C-like but there are some anomalies that can seem mysterious.<\/p>\n
Volodymyr Gubarkov has a project to provide an InteliJ plug in for AWK and part of that requires parsing AWK syntax so he has a good handle on those anomalies and why they exist. He discusses those peculiarities in his post, AWK technical notes<\/a>.<\/p>\n It\u2019s an interesting post that explains many things that you probably didn\u2019t know about AWK. In a way, it\u2019s getting into the weeds but it also increases your understanding of the way things work and allows you to write better AWK.<\/p>\n For example, one thing I didn\u2019t know was that although it\u2019s illegal to have a space between a user defined<\/i> function and its argument list, it is<\/i> legal to have a space between a built in<\/i> function and its argument list. The reason for that involves string concatenation. Take a look at Gubarkov\u2019s post for the details.<\/p>\n The post mentions some other interesting anomalies in the AWK syntax and the reasons for them. If you use AWK, it\u2019s definitely worth reading the post if only to be aware of the gotchas waiting for the unwary.<\/p>\n","protected":false},"excerpt":{"rendered":" Many of you know that I\u2019m a big fan of AWK. After Lisp and C, it\u2019s my go to language, especially for scripts that involve reading a bunch of lines and performing some sort of regex-mediated action on them. Its … Continue reading