From: Florian Weimer <fw@deneb.enyo.de>
To: Peng Yu via Libc-help <libc-help@sourceware.org>
Subject: Re: manpage of register_printf_specifier
Date: Mon, 29 Mar 2021 10:08:20 +0200 [thread overview]
Message-ID: <87lfa6wfez.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CABrM6wmEkX-CkkF3-33isCjyEhLpetq6kf9ZAvh_Kv2PZzFcxA@mail.gmail.com> (Peng Yu via Libc-help's message of "Sun, 28 Mar 2021 22:59:14 -0500")
* Peng Yu via Libc-help:
> Is there a portable way to support more format strings in printf?
No, these interfaces are very much non-standard and not widely
implemented.
prev parent reply other threads:[~2021-03-29 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 16:24 Peng Yu
2021-03-28 16:32 ` tomas
2021-03-28 16:40 ` tomas
2021-03-29 3:59 ` Peng Yu
2021-03-29 8:08 ` Florian Weimer [this message]
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=87lfa6wfez.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=libc-help@sourceware.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).