public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org,
	GNU C Library <libc-help@sourceware.org>
Subject: Re: Issue in man page clog.3
Date: Wed, 1 Nov 2023 18:08:00 +0100	[thread overview]
Message-ID: <ZUKF8Krrlf4a0sKp@debian> (raw)
In-Reply-To: <ZUJt-iwf-d9cLBGd@meinfjell.helgefjelltest.de>

[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]

On Wed, Nov 01, 2023 at 03:25:46PM +0000, Helge Kreutzmann wrote:
> Hello Alejandro,
> Am Wed, Nov 01, 2023 at 04:00:16PM +0100 schrieb Alejandro Colomar:
> > On Wed, Nov 01, 2023 at 02:02:10PM +0000, Helge Kreutzmann wrote:
> > > Without further ado, the following was found:
> > > 
> > > Issue:    [-pi,pi] means both -pi and pi are included, this does not make sense, either one must be out of the interval?
> > > 
> > > "The logarithm B<clog>()  is the inverse function of the exponential "
> > > "B<cexp>(3).  Thus, if I<y\\ =\\ clog(z)>, then I<z\\ =\\ cexp(y)>.  The "
> > > "imaginary part of I<y> is chosen in the interval [-pi,pi]."
> > 
> > I don't know this function.  Please suggest a fix, and CC glibc so that
> > they can review the change.
> 
> From a mathematical point of view either -pi or pi needs to be
> excluded. I'm not a programmer, so the I cannot tell which is the case
> here.
> 
> So you need to contact the person who wrote or who maintains this
> function / man page.

Hi,

I'm CCing glibc, in case they want to say something.

Cheers,
Alex

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

       reply	other threads:[~2023-11-01 17:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ZUJaYtPeCL1kXYwl@meinfjell.helgefjelltest.de>
     [not found] ` <ZUJoBtadvsPTwFXh@debian>
     [not found]   ` <ZUJt-iwf-d9cLBGd@meinfjell.helgefjelltest.de>
2023-11-01 17:08     ` Alejandro Colomar [this message]
2023-11-02  2:38       ` Nikolaos Chatzikonstantinou

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=ZUKF8Krrlf4a0sKp@debian \
    --to=alx@kernel.org \
    --cc=debian@helgefjell.de \
    --cc=libc-help@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.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.
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).