From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Basile Starynkevitch <basile@starynkevitch.net>,
libc-help@sourceware.org
Subject: Re: examples of customized printf
Date: Mon, 3 Jan 2022 14:04:13 -0300 [thread overview]
Message-ID: <2d754405-7aff-9fab-ca22-2ece84b3468b@linaro.org> (raw)
In-Reply-To: <9eecb822-d055-20c1-44ee-82ce83fce54a@starynkevitch.net>
On 28/12/2021 07:31, Basile Starynkevitch wrote:
> Hello all,,
>
>
> For the RefPerSys project (see http://refpersys.org/ and code on https://github.com/RefPerSys/refpersys-in-c/ ....) we need several examples of
>
>
> Customizing |printf|
>
>
> We want %V to print RpsValue_t ( intptr_t, when odd it is a tagged integer, when even and non-null it is a valid pointer to some struct).
>
>
> Examples of customizing printf for GNU guile could be enough.
>
>
>
> Happy new year 2022.
You can reference glibc own manual [1] on how to customize the printf. Keep
in mind this is a gnu extension.
[1] https://www.gnu.org/software/libc/manual/html_node/Customizing-Printf.html
prev parent reply other threads:[~2022-01-03 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 10:31 Basile Starynkevitch
2022-01-03 17:04 ` Adhemerval Zanella [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=2d754405-7aff-9fab-ca22-2ece84b3468b@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=basile@starynkevitch.net \
--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).