From: Florian Weimer <fweimer@redhat.com>
To: Jonny Grant <jg@jguk.org>
Cc: Szabolcs Nagy via Libc-help <libc-help@sourceware.org>
Subject: Re: include/stdio.h
Date: Mon, 08 Nov 2021 23:27:54 +0100 [thread overview]
Message-ID: <87pmrae105.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <476789a5-fca8-34c2-3a73-27ae85771bcf@jguk.org> (Jonny Grant's message of "Mon, 8 Nov 2021 21:45:35 +0000")
* Jonny Grant:
> May I check, I'd not expected /usr/include/stdio.h to state this, is it to state stdio is built on top of C++ iostreams nowadays?
>
> In the repo it is /glibc/libio/stdio.h
>
> "Define ISO C stdio on top of C++ iostreams"
Internally, it's still built this way. But the C++ meant here is the
C++ ABI implemented by GCC 2.95, so that aspect is now entirely useless.
We should probably remove that C++ reference from the public header.
Thanks,
Florian
next prev parent reply other threads:[~2021-11-08 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 21:45 include/stdio.h Jonny Grant
2021-11-08 22:27 ` Florian Weimer [this message]
2021-11-09 10:22 ` include/stdio.h Jonny Grant
2023-10-28 22:43 ` include/stdio.h Jonny Grant
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=87pmrae105.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=jg@jguk.org \
--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).