From: Jeff Johnston <jjohnstn@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Newlib <newlib@sourceware.org>
Subject: Re: [PATCH] math.h: Use reserved names for function parameters
Date: Fri, 25 Jun 2021 16:49:38 -0400 [thread overview]
Message-ID: <CAOox84szncSh1m0tWWkpUwsP2b2s=ymM88QqvWuDx-iznYmcQg@mail.gmail.com> (raw)
In-Reply-To: <YNYQPtzMBqJtiP3t@redhat.com>
Patch merged.
-- Jeff J.
On Fri, Jun 25, 2021 at 1:21 PM Jonathan Wakely <jwakely@redhat.com> wrote:
> Similar to 4c49accf8997da21be19be0396b2a88f33b9f949 and
> 615cf4bdce0de86e57bdc27e008a35dd713e483f this avoids the use of
> non-reserved names as function parameters. For this function the
> parameter names do actually provide useful information, because
> without the names it's not clear which parameter is the numerator and
> which the denominator. So rather than just remove the names, this
> prefixes them with double-underscores.
>
>
>
prev parent reply other threads:[~2021-06-25 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 17:19 Jonathan Wakely
2021-06-25 20:49 ` Jeff Johnston [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='CAOox84szncSh1m0tWWkpUwsP2b2s=ymM88QqvWuDx-iznYmcQg@mail.gmail.com' \
--to=jjohnstn@redhat.com \
--cc=jwakely@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).