frawk VS awk

It does, just go to the "Benchmarks" link: https://github.com/ezrosent/frawk/blob/master/info/performan...

and frawk for good measure

frawk ["frawk" in aur] - a fancier awk with support for CSV files

https://github.com/ezrosent/frawk - awk like language in rust

Frawk: A fast, JITted, statically-typed AWK written in Rust\ (27 comments)

Interesting (and a bit surprising) that the cranelift backend keeps up with LLVM backend reasonably well, especially with parallelism enabled https://github.com/ezrosent/frawk/blob/master/info/performan...

In the example I noticed a PREPARE block in addition to the well known BEGIN and END blocks. After a few minutes of searching it appears to be frawk specific:

https://github.com/ezrosent/frawk/blob/master/info/paralleli...

"Because the repeated map references are both annoying to write and inefficient to execute, frawk has a PREPARE block which executes in the worker threads at the end of its input"

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.)

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

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

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

Brian Kernighan adds Unicode support to Awk\ (143 comments)

Alas, Unicode support isn't working (yet). Unless I am missing something:

  $ git clone https://github.com/onetrueawk/awk

I'm not kidding. Just look at the code:

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

I am talking about that. You are not.

It needs the length for operations such as substring, or to apply length modifiers on regular expressions (such as \w{3,5}), which is a common thing in awk programs.

In fact, the return value of the u8_rune as implemented in the branch we are discussing (https://github.com/onetrueawk/awk/compare/unicode-support) returns a length to be used as an offset later.

This is not me saying, it's the author. There is a code comment there:

> For most of Awk, utf-8 strings just "work", since they look like null-terminated sequences of 8-bit bytes. Functions like length(), index(), and substr() have to operate in units of utf-8 characters. The u8_* functions in run.c handle this.

I know there might be different ways of doing it, but we're talking about a specific implementation.

I was wrong to assume he is storing stuff in UTF-32. He could have, but there was already code in place there to make the UTF-8 storage easier to implement.