bug-gawk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A typo in the docs


From: arnold
Subject: Re: A typo in the docs
Date: Tue, 26 Apr 2022 23:09:19 -0600
User-agent: Heirloom mailx 12.5 7/5/10

Thanks Alan for the report and Bob for help with the details.

I will get this fixed.

Arnold

Bob Proulx <bob@proulx.com> wrote:

> Alan Welsh via Bug reports only for gawk. wrote:
> > The word digit is spelled wrong here:
> > [image.png]
>
> That attachment did not survive through the mailing list to my inbox
> nor do I see it in the web archive.  I put my mailing list helper hat
> on and pulled it out of the anti-spam system archive.  It was an image
> of some of the documentation.  I'll copy the section from the online
> info pages on my system.
>
>     '\xHH...'
>          The hexadecimal value HH, where HH stands for a sequence of
>          hexadecimal digits ('0'-'9', and either 'A'-'F' or 'a'-'f').  A
>          maximum of two digts are allowed after the '\x'.  Any further
>          hexadecimal digits are treated as simple letters or numbers.
>          (c.e.)  (The '\x' escape sequence is not allowed in POSIX awk.)
>
>               CAUTION: In ISO C, the escape sequence continues until the
>               first nonhexadecimal digit is seen.  For many years, 'gawk'
>               would continue incorporating hexadecimal digits into the value
>               until a non-hexadecimal digit or the end of the string was
>               encountered.  However, using more than two hexadecimal digits
>               produced undefined results.  As of version 4.2, only two
>               digits are processed.
>
> The problem being reported looks like "digts".
>
> Alan please in the future it is always best to copy and paste in the
> plain text of things like this.  Images cannot be searched nor
> indexed.  Also the original image was very large for a mailing list
> Plain text is always best for these things.
>
> Thank you for the bug report.
>
> Bob
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]