From: Basile Starynkevitch <basile@starynkevitch.net>
To: libc-help@sourceware.org
Subject: examples of customized printf
Date: Tue, 28 Dec 2021 11:31:00 +0100 [thread overview]
Message-ID: <9eecb822-d055-20c1-44ee-82ce83fce54a@starynkevitch.net> (raw)
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.
NB. I also dream of finding European partners for RefPerSys within some
HorizonEurope consortium. Then contact me by email (perhaps at office,
CEA LIST, to basile.starynkevitch@cea.fr)
--
Basile Starynkevitch<basile@starynkevitch.net>
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/
next reply other threads:[~2021-12-28 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 10:31 Basile Starynkevitch [this message]
2022-01-03 17:04 ` Adhemerval Zanella
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=9eecb822-d055-20c1-44ee-82ce83fce54a@starynkevitch.net \
--to=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).