From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: Issue: #include <stdio.h> shall not cause intmax_t to be defined
Date: Fri, 6 May 2022 11:14:09 +0200 [thread overview]
Message-ID: <YnTm4QgPjdfOLHfX@calimero.vinschen.de> (raw)
In-Reply-To: <CAL9Mx1sv6jE3LxChMGT=_KLs8Vk_cAYCP7Tv+HyhEO-r24Nzeg@mail.gmail.com>
On May 5 19:15, Pavel M wrote:
> > Is there actually a "MUST NOT" defined anywhere in the standards or was
> this change unnecessary?
> C11 specifies when header X includes header Y.
> Examples:
> 7.25 Type-generic math <tgmath.h>:
> > The header <tgmath.h> includes the headers <math.h> and <complex.h>
> 7.26 Threads <threads.h>:
> > The header <threads.h> includes the header <time.h>
> 7.8 Format conversion of integer types <inttypes.h>:
> > The header <inttypes.h> includes the header <stdint.h>
> There are no more occurrences of "includes the header".
These examples define a MUST, where exposure of certain other header
file definitions are expected by including a single other header.
None of them defines a MUST NOT, which means that certain types
are not to be exposed when including a certain other header.
But, either way, the situation should be cleared by Sebastians patch.
Corinna
prev parent reply other threads:[~2022-05-06 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 21:41 Pavel M
2022-05-03 17:00 ` Corinna Vinschen
2022-05-04 7:59 ` Sebastian Huber
2022-05-04 8:37 ` Corinna Vinschen
2022-05-04 8:41 ` Sebastian Huber
2022-05-04 8:54 ` Corinna Vinschen
2022-05-04 9:02 ` Sebastian Huber
2022-05-04 13:12 ` Corinna Vinschen
2022-05-05 16:15 ` Pavel M
2022-05-06 9:14 ` Corinna Vinschen [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=YnTm4QgPjdfOLHfX@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@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).