From: Mike Frysinger <vapier@gentoo.org>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>,
newlib@sourceware.org
Subject: Re: [PATCH] build: Avoid length() GNU awk extension
Date: Wed, 9 Mar 2022 04:10:17 -0500 [thread overview]
Message-ID: <Yihu+fA/bJ2TVNLO@vapier> (raw)
In-Reply-To: <YihrS9u/4oDnYKyB@vapier>
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]
On 09 Mar 2022 03:54, Mike Frysinger wrote:
> On 09 Mar 2022 08:31, Sebastian Huber wrote:
> > Other awk implementations such as mawk do not support the length() function.
>
> those awk implementations are not POSIX compliant. length() is
> *not* a GNU extension. you can see it clearly defined in POSIX:
> https://pubs.opengroup.org/onlinepubs/9699919799/utilities/awk.html#tag_20_06_13_13
sorry, i quoted length() as used to count bytes in a string, not elements
in an array. POSIX doesn't support that. i would still argue that, while
gawk supports it, it isn't a GNU extension. bwk supported it back in 2002,
and gawk didn't implement it until ~2005.
> that said, mawk does support length(), and has since at least 2008 in
> the 1.3.3 release. i stopped looking back further in the history.
the original mawk has been dead for over a decade. i hope you're not trying
to use such vintage tools. Thomas E. Dickey picked up maintenance and has
produced a series of fixes & improvements, and every distro i'm aware of is
using his fork.
https://invisible-island.net/mawk/
i mention this because he implemented length() to count array elements back
in 2012. so if you still haven't updated to a version that supports that,
you should really get on top of that.
all that said, the patch you propose is a simple alternative that is POSIX
compliant, so i'm fine with it too.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-03-09 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 7:31 Sebastian Huber
2022-03-09 8:26 ` Corinna Vinschen
2022-03-09 8:54 ` Mike Frysinger
2022-03-09 9:02 ` Sebastian Huber
2022-03-09 9:10 ` Mike Frysinger [this message]
2022-03-09 10:03 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yihu+fA/bJ2TVNLO@vapier \
--to=vapier@gentoo.org \
--cc=newlib@sourceware.org \
--cc=sebastian.huber@embedded-brains.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).