From: Florian Weimer <fweimer@redhat.com>
To: Yair Lenga via Gcc <gcc@gcc.gnu.org>
Cc: Yair Lenga <yair.lenga@gmail.com>
Subject: Re: Gcc Digest, Vol 29, Issue 7
Date: Tue, 05 Jul 2022 14:16:38 +0200 [thread overview]
Message-ID: <87bku33gbd.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAK3_KpNqaea8U+N+5Z=i+-wrEzoryhXCaEnkjsWCzOeWiYcQtQ@mail.gmail.com> (Yair Lenga via Gcc's message of "Tue, 5 Jul 2022 10:19:59 +0300")
* Yair Lenga via Gcc:
> My question: does anyone know how much effort it will be to add a new GCC
> built-in (or extension), that will automatically generate a descriptive
> format string, consistent with scanf formatting, avoiding the need to
> manually enter the formatting string.
It's already possible to do this with C++. Can't you just use C++
instead?
Thanks,
Florian
next prev parent reply other threads:[~2022-07-05 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1656936003.1843426.gcc@gcc.gnu.org>
2022-07-05 7:19 ` Yair Lenga
2022-07-05 12:16 ` Florian Weimer [this message]
2022-07-05 21:24 ` Yair Lenga
2022-07-07 10:02 ` Safer vararg calls Florian Weimer
2022-07-05 21:52 ` Gcc Digest, Vol 29, Issue 7 Andrew Pinski
2022-07-06 7:17 ` David Brown
2022-07-06 7:59 ` Yair Lenga
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=87bku33gbd.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=yair.lenga@gmail.com \
/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).