Path: csiph.com!news.mixmin.net!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.std.c
Subject: Re: What is the point of restrict in fopen?
Date: Thu, 20 Jul 2023 10:17:37 -0700
Organization: A noiseless patient Spider
Lines: 11
Message-ID: <86cz0mzemm.fsf@linuxsc.com>
References: <20230524162836.172@kylheku.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: dont-email.me; posting-host="3857442d865f8a7bff3454fde02b814b"; logging-data="2949588"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+4um90phf1QarLebHlc+r5jsWOhcg1l3A="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:qqIIgbXoeRmJs+9CcxqjY9tD1A8= sha1:cJXpqmJYWqVAILavJuv2wYSiGL0=
Xref: csiph.com comp.std.c:6501

Kaz Kylheku <864-117-4973@kylheku.com> writes:

> I've noticed that both arguments of fopen are restrict-qualified.

What I think you mean is that the arguments given in the prototype
declaration in the C standard are qualified with the 'restrict'
keyword.

Note that this form of declaration has no effect on the semantics of
the function.  The function declaration, and its semantics, are just
the same as if the uses of 'restrict' were removed.