Subject: Re: bin/29226: /etc/daily pipes >32bit integers from netstat to awk, which can't deal with them
To: None <firstname.lastname@example.org, email@example.com,>
From: Christos Zoulas <firstname.lastname@example.org>
Date: 02/04/2005 09:14:41
On Feb 4, 1:53pm, email@example.com (Klaus Klein) wrote:
-- Subject: Re: bin/29226: /etc/daily pipes >32bit integers from netstat to a
| The following reply was made to PR bin/29226; it has been noted by GNATS.
| From: Klaus Klein <firstname.lastname@example.org>
| To: email@example.com
| Subject: Re: bin/29226: /etc/daily pipes >32bit integers from netstat to awk, which can't deal with them
| Date: Fri, 4 Feb 2005 14:46:58 +0100
| On Fri, Feb 04, 2005 at 08:17:00AM +0000, firstname.lastname@example.org wrote:
| > (1) Teach awk 64bit number handling, including quad conversions.
| Shell utilities seem a bad place to instill knowledge of explicit
| integer size conversions.
| > (1) Replace awk in /etc/daily with something that can deal with
| > large numbers
| I wouldn't mind awk(1) using intmax_t internally; however, there is
| a showstopper in IEEE Std 1003.1-2001 section 1.7.2:
| "Integer variables and constants, including the values of
| operands and option-arguments, used by the standard
| utilities [...] shall be implemented as equivalent to
| the ISO C standard _signed long_ data type [...]"
| Having an alternate, conforming version in, say, /usr/posix/bin and
| adjusting _CS_PATH accordingly might do the trick for this one (and
| a couple of similar issues).
Or a flag, if that does not make the code too difficult to handle.