awk VS bwk

Awk now supports a `--csv` flag for processing csv's. https://github.com/onetrueawk/awk/blob/master/README.md

Right, "the one true awk" corresponds to a book written in 1988, very explicity. https://github.com/onetrueawk/awk

You were the one that that said POSIX awk to begin with, I was using your terms.

As far as shitting on the GMU tools, I don't think I've seen someone do that for over 20 years.

This is not a productive conversation. You can live life however you want

I also wrote a small program to benchmark and check the solutions across different Awk implementations (see the image). I use the macos system awk (which is pretty close to https://github.com/onetrueawk/awk if I'm not mistaken) as a reference (the first column), so all solutions had to work with that.

A simpler Yacc grammar is awk/awkgram.y.

Neat, this is now the third year I'm using awk and still learning new tricks. (I'm using awk as the reference, so I don't use gnu extensions.)

I did this in nawk, which doesn't support extended regular expressions. If instead you're using gawk, which does, check out \b for word boundaries in extended regular expressions. The [^a-z][a-z] approach you showed consumes the prior character.

BWK’s commit and test files (mentioned in the video)

https://github.com/onetrueawk/awk/commit/d3a19e6f2533d479841...

git clone -b unicode-support https://github.com/onetrueawk/awk.git

This is dumb as fuck. Brian Kernighan of K&R (The C Programming Language) is 80 and he’s still more intelligent than any of you retards. Mf just submitted a patch to awk a couple months ago https://github.com/onetrueawk/awk

The Unicode branch: https://github.com/onetrueawk/awk/tree/unicode-support

Document the steps to setup dev environment in your own words and highlight the issues that you run into

Lots of people are commenting saying they have problems with this.

The first thing I do when working on an unfamiliar project is to write a SHELL SCRIPT that records everything I did. I keep that at the root of the git repo, usually as "run.sh".

For example here is what I did when hacking on Kernighan's awk 5 years ago:

https://github.com/andychu/bwk/blob/master/run.sh

So now 5 years later I can see exactly where I got the files from. And I usually count how much source code there is in a repo to get a feel for it, and I have that exact command.

And I was trying to figure out how much test coverage there is, so I ran a bunch of gcov stuff, which involve Python.

The shell script may not work now, but the point is that I can tell within 10 seconds what I did 5 years ago.

So basically I suggest becoming SHELL LITERATE and checking in shell script with comments. (You can also use a Makefile, but shell is less prescriptive about its model and has fewer gotchas. Make has all the gotchas of shell plus some more.)

https://news.ycombinator.com/item?id=25400278