mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Jens Gustedt <jens.gustedt@inria.fr>
To: musl@lists.openwall.com,Rich Felker <dalias@libc.org>
Subject: Re: [PATCH] stdio: implement fopencookie(3)
Date: Wed, 11 Oct 2017 07:51:17 +0200	[thread overview]
Message-ID: <A76B0B8C-9E75-43FE-AB98-DFDE7CA3F9FE@inria.fr> (raw)
In-Reply-To: <20171011020808.GK1627@brightrain.aerifal.cx>

Am 11. Oktober 2017 04:08:08 MESZ schrieb Rich Felker <dalias@libc.org>:
>On Tue, Oct 10, 2017 at 11:40:15PM +0200, Jens Gustedt wrote:
>> Hello Rich,
>> 
>> On Tue, 10 Oct 2017 16:56:54 -0400 Rich Felker <dalias@libc.org>
>wrote:
>> 
>> > Also note that while standard functions in POSIX can additionally
>be
>> > defined as function-like macros, they can't be object-like macros,
>so
>> > (*read), etc. are safe due to the parentheses.
>> 
>> They would only be safe in the header. They are not safe on the using
>> side, I think. Something like
>> 
>>     toto->read = whatever;
>> 
>> or
>> 
>>     *toto = (cookie_io_functions_t){ .read = another, }
>> 
>> can't be protected by parenthesis.
>
>It doesn't have to be, because it doesn't have the token ( immediately
>following it.

I meant this as an example where an object-like macro would hurt. "read" is a bad example, because it is reserved. But if an application had an object-like  macro "seek" it would be screwed.

Jens 

-- 
Jens Gustedt - INRIA & ICube, Strasbourg, France


  reply	other threads:[~2017-10-11  5:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10 18:03 William Pitcock
2017-10-10 18:51 ` Jens Gustedt
2017-10-10 20:56   ` Rich Felker
2017-10-10 21:40     ` Jens Gustedt
2017-10-11  2:08       ` Rich Felker
2017-10-11  5:51         ` Jens Gustedt [this message]
2017-10-10 22:58     ` Morten Welinder
2017-10-11  2:09       ` Rich Felker
  -- strict thread matches above, loose matches on Subject: below --
2017-10-10 23:27 William Pitcock
2017-10-05  6:48 William Pitcock
2017-10-05 10:10 ` Szabolcs Nagy

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=A76B0B8C-9E75-43FE-AB98-DFDE7CA3F9FE@inria.fr \
    --to=jens.gustedt@inria.fr \
    --cc=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).