Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
References: <5382FD21.6040600@clear.net.nz>
            <CANQYN6zOq8dd5BUi32nCJGh9QgagZaaoj4UW1Ku3B4XWHi2PNA@mail.gmail.com>
Message-ID:  <A11620FE-AE5E-4CF7-A014-A5C5D4E05121@gmail.com>
Date:         Tue, 27 May 2014 08:24:07 +0930
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Will Robertson <wspr81@GMAIL.COM>
Subject: Re: l3fp and sin(pi), cos(pi/2)
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <CANQYN6zOq8dd5BUi32nCJGh9QgagZaaoj4UW1Ku3B4XWHi2PNA@mail.gmail.com>
Precedence: list
Content-Transfer-Encoding: quoted-printable
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

On 27 May 2014, at 3:11 am, Bruno Le Floch <blflatex@GMAIL.COM> wrote:

> Short answer: use the trigonometric functions which expect arguments
> in degrees: sind, cosd, tand,...  sind(180) correctly gives -0.

I came across this the other day and had been going to ask =97 while I am=
 certainly okay with receiving this result in a computational sense, I wo=
nder about the typesetting; should/can we provide an easy way to typeset =
negative zero just as zero?

When I was trying it out, I thought perhaps that \fp_eval:n would return =
negative zero but \fp_to_decimal:n would =93normalise=94 it; is that a cr=
azy idea?

Cheers,
Will