From: Florian Weimer <fw@deneb.enyo.de>
To: DJ Delorie <dj@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [patch v3] aligned_alloc: conform to C17
Date: Tue, 21 Mar 2023 20:08:37 +0100 [thread overview]
Message-ID: <87v8it3osq.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <xnwn3ayp11.fsf@greed.delorie.com> (DJ Delorie's message of "Tue, 21 Mar 2023 13:47:54 -0400")
* DJ Delorie:
> Florian Weimer <fw@deneb.enyo.de> writes:
>> I'm surprised that this even compiles. This sort of makes the
>> function static and gives it external linkage.
>
> It almost does the same thing as your example, but follows the
> internal/external paradigm we've been using for all the other functions.
>
> (in your example, just drop the "static", then it's the same)
>
> And yes, it took Carlos and I a while to go through all this linkage
> stuff to make sure we understood it.
Yeah, the static was wrong. I think you should avoid the alias if
there aren't any internal calls.
next prev parent reply other threads:[~2023-03-21 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 4:47 DJ Delorie
2023-03-21 17:28 ` Florian Weimer
2023-03-21 17:47 ` DJ Delorie
2023-03-21 19:08 ` Florian Weimer [this message]
2023-03-21 20:21 ` DJ Delorie
2023-03-21 20:43 ` Florian Weimer
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=87v8it3osq.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=dj@redhat.com \
--cc=libc-alpha@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).