From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Why are stdin/stdout/stderr `FILE *const` in musl?
Date: Fri, 2 Feb 2018 12:35:01 -0500 [thread overview]
Message-ID: <20180202173501.GS1627@brightrain.aerifal.cx> (raw)
In-Reply-To: <1E109BA9-57C0-42DB-9B43-8ADE27F9E76C@hanauska.name>
On Fri, Feb 02, 2018 at 02:24:28PM +0100, CodingMarkus wrote:
> Hello everyone!
>
> Just a quick question:
> Why does musl define stdin, stdout, and stderr to be of type `FILE
> *const`? Neither the C standard, nor the POSIX standard require,
They don't require it, but they allow it. musl's implementation _does_
require it, because behind the macros (all the C standard requires to
exist) are const-qualified objects (living inside libc.so/libc.a), and
declaring them with a type that mismatches their definitions would
result in undefined behavior.
> recommend or even imply that it would be allowed that this is a
> `const` pointer. That’s why other C libraries define it as `FILE *`
> only because that matches the examples given by POSIX and that
> matches the description found in any ISO-C standard. Making them
> const only break compatibility with other C libraries, e.g.
> considered this code:
>
> void * getOutputPtr ( void ) {
> if (/* whatever */) {
> return &stdout;
> }
> return &stderr;
> }
>
> This code is correct by C standard and it is correct by POSIX
It's not. As others have noted, stderr is not specified as an object;
it's a macro that expands to an expression with type FILE *. You
cannot take the address of an expression in general.
Rich
prev parent reply other threads:[~2018-02-02 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 13:24 CodingMarkus
2018-02-02 13:54 ` Jens Gustedt
2018-02-02 14:13 ` Alexander Monakov
2018-02-02 15:01 ` Markus Wichmann
2018-02-02 15:30 ` CodingMarkus
[not found] ` <CAOUYtQAWqEY_Ys3crsyXDmVVqJVjfzwTA0NsDxfpgU5cP_t2nA@mail.gmail.com>
2018-02-02 15:53 ` Jon Chesterfield
2018-02-02 16:01 ` Jens Gustedt
2018-02-02 16:12 ` Jeff Hammond
2018-02-02 17:16 ` William Pitcock
2018-02-02 17:35 ` Rich Felker [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=20180202173501.GS1627@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).