3 ms·
Anything too big to be coded with AWK should be done in Perl. Nothing bad about that. Perl it's almost a sed/awk/sh replacement when shell scripting based code
by anthk 4y ago
Anything too big to be coded with AWK should be done in Perl. Nothing bad about that. Perl it's almost a sed/awk/sh replacement when shell scripting based code gets clunky.
- 082349872349872 4y agoSpeaking of sed/awk/sh, in this case precomposing the awk with a sed preprocessor (in a sh pipeline) will give you both data structures (awk) and capture groups (sed).
- jabl 4y agoIMHO the nice thing about sed&awk is that a quick cheatsheet that covers most usage fits nicely on one page. Perl, in contrast, is more a 'proper' language and the Camel book is a pretty chunky tome. If you're going through all the trouble of learning a language in that space, you might as well go with something like python. Though admittedly python isn't a very good sed/awk replacement.
- kqr 4y agoWho said you had to learn the entirety of Perl? I've been using Perl as an awk replacement for soon five years and I barely know a lick of Perl outside of what I need to use it as awk. If you use it that way, it's a much smaller language. (That said, I do still have the tabs of perldata, perlobj, perlmod, and perlop open because I want to learn it better.)
- rtpg 4y agoWhat does this look like in practice? Does Perl have a similar control flow syntax to awk?
- jrumbut 4y agoIt actually does (to an extent). There are BEGIN and END blocks (not used that much in regular scripting but they exist). There are also a bunch of perl command flags that can make things more awk-ish or sed-ish. This random blog post gives something of the flavor. https://lifecs.likai.org/2008/10/using-perl-like-awk-and-sed.html https://lifecs.likai.org/2008/10/using-perl-like-awk-and-sed...
- kqr 4y agoThere's one fairly obvious error in that article: the fields are $F[0] etc, not @F[0]. Otherwise yes, that's a good way to make Perl look like awk. I personally translate awk concepts to more idiomatic Perl (I had no idea about -MEnglish, for example) but the concepts are still the same.
- jrumbut 4y agoYou're right, but it will still work as written.
- tyingq 4y ago> awk '/foo=([0-9]+)/ { print $1 }' The equivalent Perl isn't that far off from the above. perl -nE '/foo=([0-9]+)/ && say $1'
- recuter 4y agoAbsolutely nothing should be done with Perl, it is 2023. If you're jonesing for a sed replacement (it even has capture groups) try: https://github.com/chmln/sd https://github.com/chmln/sd Worth being aware of: https://github.com/theryangeary/choose https://github.com/theryangeary/choose https://github.com/nushell/nushell https://github.com/nushell/nushell
- zajio1am 4y agoSo obscure tools that are not packaged even in Debian?
- recuter 4y ago22k stars is not really that obscure not that it matters. I didn't realize we are forever limiting ourselves to tools written in the 70s and 80s my apologies. Would you consider trying something other than Perl once it is no longer packaged for you? Because it is an x-language, bereft of life.
- nrclark 4y agoUse the tools you like. It's nobody's place to tell you what tools to use, and the reverse of that is also true. For a lot of us, we want to develop scripts (and skills) that are portable across different environments. There are limited hours in a workday, and I get the most value out of learning (and using) tools that I can find on the servers / build-machines / workstations that I have to use every day. Those machines run Ubuntu, Debian, Rocky, and RHEL. Yes, it's a slow process to get new packages into mainstream distros. That's not a bad thing, because those packages have to be maintained for a very long time. Stability is a virtue here. There are some ecosystems (I'm looking at you, Javascript) where anything older than a year might as well be abandonware. It's great that there are some fast-moving areas in our industry, and also great that there are slow-moving areas. Don't make the mistake of assuming something is bad just because it's feature-complete. You might be surprised at how feature-rich something like Awk really is. If your argument boils down to "Awk and Bash are ugly and outdated", I'd encourage you to think more flexibly about the tools you choose. There's nothing wrong with learning the basics of a widespread tool that you are guaranteed to find anywhere.
- zajio1am 4y agoWhy? Perl has cryptic syntax, while AWK has syntax that is easily understood by anyone that has experience with common programming languages like C, C++, Java. If you find unknown syntax construct in Perl code, it is hard to identify what it is, but if you find unknown function in AWK, you can just google its name. Also, AWK is mandated by POSIX, so one can assume it is installed, while Perl is optional.
- ykonstant 4y agoMaybe, but what comex and I are talking about isn't too big to be coded in Awk; it is a very (extremely) common pattern that Awk just makes more difficult than it needs to be.
- b3morales 4y agoI don't regularly use either language, but I prefer to use Ruby for this: https://robm.me.uk/2013/11/ruby-enp/ https://robm.me.uk/2013/11/ruby-enp/ Example from that article $ echo "foo\nbar\nbaz" | ruby -ne 'BEGIN { i = 1 }; puts "#{i} #{$_}"; i += 1' output 1 foo 2 bar 3 baz
- alganet 4y agoA capture group is not "too big", sed has them. It's a reasonable feature request for a small tool. sh, awk and sed are fine. They are easy, small, powerful tools that are easy to compile and understand. Perl, python, nushell, etc. The options listed here are great if you're writing cute snippets on the terminal or hacking together some higher level automation. These more elaborate tools, however, are terrible if you're trying to be lean in the build/bootstrap process and have a small set of auditable, easy-to-compile tools. The graph on this page illustrate the bootstraping problem well: https://bootstrappable.org/projects/mes.html https://bootstrappable.org/projects/mes.html These small 50+ years UNIX tools that have zero build dependencies are around for a reason: they are small and have zero build dependencies.