In article <sf2ide$ab7$
1...@news-1.m-online.net>,
Janis Papanagnou <
janis_pa...@hotmail.com> wrote:
>On 12.08.2021 09:02, Laurent MANCHON wrote:
>> on unix machine i don't like gawk i prefer mawk which is faster than gawk.
>
>Is that true? - I know of some performance tests (done by Andrew Sumner
>20+ years ago) where that was actually not the case - some test cases
>were faster, some slower -, and since then a lot of optimizations have
>been done in GNU Awk (including byte code support).
Historically, it is (has been) definitely true. Historically, mawk was
always considered very fast, and GAWK was originally designed to be
feature-rich and not have limits (which are common attributes/goals of GNU
software) at the expense of being big and not particularly efficient.
Note, incidentally, that bash also fits this profile. I like bash for its
many nice features, but its own man page says that it is too big and too
slow.
However, this situation may have changed over the years. As you say,
effort has gone into making GAWK more runtime efficient.
>> and on windows, compiled program with Tawk v6.7 are faster than gawk.
1) It is unlikely that speed really is an issue. Most people who think it
is (in pretty much all contexts), turn out to be misguided. If you want
efficiency, writing in AWK is probably not what you should be doing in the
first place.
But, that said, it is true (and yes, I am sort of contradicting myself),
TAWK is very very efficient and fast. This is a good reason to use TAWK,
if you can. I think it is indisputable that TAWK is the best/fastest
significant AWK implementation.
>If speed is a critical issue you may also try awka, an Awk compiler.
I don't think awka - or any other so-called "awk compiler" - makes any
claims to making your program run faster. Aren't they all just for
encryption (aka, code security) purposes?
BTW, all this talk by you and your c.l.a friend which are of the strain
"Why don't you just use GAWK like we do?" are misguided. If the OP has and
is using TAWK, he should continue to do so.
--
The randomly chosen signature file that would have appeared here is more than 4
lines long. As such, it violates one or more Usenet RFCs. In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
http://user.xmission.com/~gazelle/Sigs/DanaC