From: Rich Felker <dalias@libc.org>
To: Damian McGuckin <damianm@esi.com.au>
Cc: musl@lists.openwall.com
Subject: Re: [musl] cproj.c in 1.2.2
Date: Tue, 18 Jan 2022 10:04:35 -0500 [thread overview]
Message-ID: <20220118150435.GE7074@brightrain.aerifal.cx> (raw)
In-Reply-To: <alpine.LRH.2.02.2201182038560.9986@key0.esi.com.au>
On Tue, Jan 18, 2022 at 08:46:25PM +1100, Damian McGuckin wrote:
>
> In the event that 'z' is mapped to the unit sphere, the code says
>
> CMPLX(INFINITY, copysign(0.0, creal(z)))
>
> Isn't the definition
>
> CMPLX(INFINITY, copysign(0.0, cimag(z)))
>
> Or am I wrong?
>
> Ditto for cprojf.c and cprojl.c.
I don't think you're wrong and I'm pretty sure this was just a mistake
in the original writing of the complex code. I'll fix it.
Rich
prev parent reply other threads:[~2022-01-18 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 9:46 Damian McGuckin
2022-01-18 15:04 ` 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=20220118150435.GE7074@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=damianm@esi.com.au \
--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).