From: Florian Weimer <fweimer@redhat.com>
To: Yair Lenga <yair.lenga@gmail.com>
Cc: Yair Lenga via Gcc <gcc@gcc.gnu.org>
Subject: Re: Safer vararg calls
Date: Thu, 07 Jul 2022 12:02:02 +0200 [thread overview]
Message-ID: <87a69l6y1x.fsf_-_@oldenburg.str.redhat.com> (raw)
In-Reply-To: <16B925A2-D5E5-4731-AE79-6E6253DB350B@gmail.com> (Yair Lenga's message of "Wed, 6 Jul 2022 00:24:34 +0300")
* Yair Lenga:
> I prefer not to go into “flame wars” on the merits of C vs C++. My
> projects are (mostly) in “C” and I am happy with this setup. In
> addition, given technical / organizational / business issues,
> switching to C++ not an option.
Sure, but you could at least use C++ to prototype the implementation and
even the ABI.
Thanks,
Florian
next prev parent reply other threads:[~2022-07-07 10:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1656936003.1843426.gcc@gcc.gnu.org>
2022-07-05 7:19 ` Gcc Digest, Vol 29, Issue 7 Yair Lenga
2022-07-05 12:16 ` Florian Weimer
2022-07-05 21:24 ` Yair Lenga
2022-07-07 10:02 ` Florian Weimer [this message]
2022-07-05 21:52 ` Andrew Pinski
2022-07-06 7:17 ` David Brown
2022-07-06 7:59 ` Yair Lenga
2022-06-21 10:16 Safer vararg calls Yair Lenga
2022-06-21 10:43 ` Jonathan Wakely
2022-06-25 14:27 ` 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=87a69l6y1x.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).