![]() ![]() I think this argument is unfairly dismissive. It's true enough for the 20 minute version though. I've written awk scripts a couple hundred lines in the past. ![]() ![]() I know, not really, and especially for gawk. I can't say the same of perl, even when I was more familiar with it.Ĭaveat: awk, nawk, mawk, and gawk don't necessarily share the same set of corner cases, and you may not get error messages that make sense to you when you bump into one with an unfamiliar awk. For basic stuff, the fact that that's basically all awk does means there's so many fewer ways to do it wrong. I know I can use perl for what I use awk for, and when I've raised this point before, people have been quick to explain how to process input by lines, and conditionally do something. perl, by contrast, is far too large to fit in my head and comes with an ecosystem that is much larger still. And if I forget, it only takes 20 minutes to put them back in. Why? awk is small enough that it fits in my head, or at least the bits I need every couple of months do. At some point, I bit the bullet and learned awk, and I've mostly abandoned perl as a result. I learned perl in college in the 5.6 days, and did a lot of text processing with it for a time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |