mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] [PATCH] complex: fix comment in cacosh
Date: Sun, 10 Mar 2024 17:19:06 -0400	[thread overview]
Message-ID: <20240310211906.GV4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <20240310200040.GF1884416@port70.net>

On Sun, Mar 10, 2024 at 09:00:40PM +0100, Szabolcs Nagy wrote:
> The principal experssions defining acosh and acos are such that
> 
>   acosh(z) = +-i acos(z)
> 
> where the + is only true on the Im(z)>0 half of the complex plane
> (and partly on Im(z)==0 depending on number representation).
> 
> fix the comment without expanding on the details.
> ---
>  src/complex/cacosh.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/src/complex/cacosh.c b/src/complex/cacosh.c
> index 76127f75..586328ce 100644
> --- a/src/complex/cacosh.c
> +++ b/src/complex/cacosh.c
> @@ -1,6 +1,6 @@
>  #include "complex_impl.h"
>  
> -/* acosh(z) = i acos(z) */
> +/* acosh(z) = +-i acos(z) */
>  
>  double complex cacosh(double complex z)
>  {

I'm fine with taking this patch as-is, but it naturally raises a
question: should it instead be:

-/* acosh(z) = i acos(z) */
+/* acosh(z) = ±i acos(z) */

IOW, should we use non-ascii characters in comments like this? My
leaning would be yes, especially since it may be needed to properly
attribute an algorithm or something where the only alternative is
misspelling someone's name or leaving it out entirely.

Really the only consideration for not doing this would be if it
actively breaks compiling in some environments, but I don't think
that's the case.

Rich

  reply	other threads:[~2024-03-10 21:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-10 20:00 Szabolcs Nagy
2024-03-10 21:19 ` Rich Felker [this message]
2024-03-10 23:29   ` Thorsten Glaser
2024-03-11  8:38   ` Szabolcs Nagy
2024-03-11  8:43     ` Damian McGuckin
2024-03-11 12:20       ` Gabriel Ravier
2024-03-11 13:15         ` Damian McGuckin

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=20240310211906.GV4163@brightrain.aerifal.cx \
    --to=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).