From: Alex Colomar <alx.manpages@gmail.com>
To: linux-man@vger.kernel.org, libc-alpha@sourceware.org
Cc: Walter Harms <wharms@bfs.de>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: [RFC v2] register_printf_speficier.3, register_printf_modifier.3, register_printf_type.3: Add new manual page and links
Date: Mon, 19 Sep 2022 10:55:25 +0200 [thread overview]
Message-ID: <3ae80927-8f7c-1b8d-1764-ba19bf65c5b6@gmail.com> (raw)
In-Reply-To: <20220918230901.24488-1-alx.manpages@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 539 bytes --]
On 9/19/22 01:09, Alex Colomar wrote:
> Suggested-by: Walter Harms <wharms@bfs.de>
> Signed-off-by: Alex Colomar <alx.manpages@gmail.com>
> ---
>
> v2:
>
> - bug about padding zeros fixed. But UB about 'l', 'll' (and 'j', 'z') not.
>
>
I found the reason of the bug. It seems I didn't correctly understand
printf_arginfo_size_funtion (as I suspected). I had to OR
PA_FLAG_LONG[_LONG]. Now it works fine. I'll update the page, and send
it later.
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-09-19 8:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 22:16 [PATCH] register_printf_speficier.3, register_printf_modifier.3, register_printf_type.3: Add new manual page and links Alex Colomar
2022-09-18 22:36 ` Alex Colomar
2022-09-18 22:38 ` Alex Colomar
2022-09-18 23:09 ` [RFC v2] " Alex Colomar
2022-09-19 8:55 ` Alex Colomar [this message]
2022-09-18 23:18 ` [PATCH] " G. Branden Robinson
2022-09-18 23:25 ` Alex Colomar
2022-09-19 16:54 ` [RFC v3 0/4] Document <printf.h> Alex Colomar
2022-09-19 16:54 ` [RFC v3] printf.3head: Document functions for customizing printf(3)-like functions Alex Colomar
2022-09-19 16:54 ` [RFC v3 2/4] register_printf_specifier.3, register_printf_modifier.3, register_printf_type.3: Add links to printf.h(3head) Alex Colomar
2022-09-19 16:54 ` [RFC v3 3/4] printf_arginfo_size_function.3type, printf_function.3type, printf_info.3type, printf_va_arg_function.3type: " Alex Colomar
2022-09-19 16:54 ` [RFC v3 4/4] PA_CHAR.3const, PA_DOUBLE.3const, PA_FLAG_LONG.3const, PA_FLAG_LONG_DOUBLE.3const, PA_FLAG_LONG_LONG.3const, PA_FLAG_PTR.3const, PA_FLAG_SHORT.3const, PA_FLOAT.3const, PA_INT.3const, PA_LAST.3const, PA_POINTER.3const, PA_STRING.3const, PA_WCHAR.3const, PA_WSTRING.3const: " Alex Colomar
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=3ae80927-8f7c-1b8d-1764-ba19bf65c5b6@gmail.com \
--to=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=wharms@bfs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.