[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-gawk] Invalid result when converting to hex literal
From: |
Arnold Robbins |
Subject: |
Re: [bug-gawk] Invalid result when converting to hex literal |
Date: |
Thu, 22 Mar 2018 20:10:18 +0200 |
User-agent: |
Heirloom mailx 12.5 6/20/10 |
I wrote:
> Harumph. I think the standard used to be more explicit about which
> specifiers were required in awk and which not, but I may be wrong.
>
> So indeed, basic language lawyering leads us to undertstand that POSIX
> wants %a in awk.
>
> At the moment, I don't think any awk implements this. Additionally,
> it is problematic to do so on some older-but-still-supported platforms,
> since this requires support in the underlying C library that may
> be missing.
>
> I will have to think about this.
I have implemented and documented %a and %A support. It's now pushed
out to the git repo.
C99 floating point hex constants will have to wait for another day.
Thanks,
Arnold
- [bug-gawk] Invalid result when converting to hex literal, Steven Penny, 2018/03/20
- Re: [bug-gawk] Invalid result when converting to hex literal, arnold, 2018/03/20
- Re: [bug-gawk] Invalid result when converting to hex literal, arnold, 2018/03/20
- Re: [bug-gawk] Invalid result when converting to hex literal, Nelson H. F. Beebe, 2018/03/20
- Re: [bug-gawk] Invalid result when converting to hex literal, Steven Penny, 2018/03/20
- Re: [bug-gawk] Invalid result when converting to hex literal, arnold, 2018/03/20
- Re: [bug-gawk] Invalid result when converting to hex literal, Steven Penny, 2018/03/20
- Re: [bug-gawk] Invalid result when converting to hex literal, arnold, 2018/03/21
- Re: [bug-gawk] Invalid result when converting to hex literal, Nelson H. F. Beebe, 2018/03/21
- Re: [bug-gawk] Invalid result when converting to hex literal, arnold, 2018/03/22
- Re: [bug-gawk] Invalid result when converting to hex literal,
Arnold Robbins <=
- Re: [bug-gawk] Invalid result when converting to hex literal, arnold, 2018/03/21