[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-gawk] Invalid result when converting to hex literal
|
From: |
Steven Penny |
|
Subject: |
Re: [bug-gawk] Invalid result when converting to hex literal |
|
Date: |
Tue, 20 Mar 2018 13:32:28 -0500 |
On Tue, Mar 20, 2018 at 11:36 AM, Nelson H. F. Beebe wrote:
> It seems to me that hexadecimal floating point values are still not
> correctly supported in gawk, even though the manual suggests that they
> SHOULD BE when the --non-decimal-data option is supplied.
I agree with this. another known POSIX violation is that Gawk does not
Currently support the "%a" conversion specifier:
http://stackoverflow.com/q/41917046/a-conversion-specifier-not-recognized
- [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 <=
- 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, 2018/03/22
- Re: [bug-gawk] Invalid result when converting to hex literal, arnold, 2018/03/21