From: luigi scarso via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: luigi scarso <luigi.scarso@gmail.com>
Subject: Re: atan2 function
Date: Fri, 14 Oct 2022 15:05:18 +0200 [thread overview]
Message-ID: <CAG5iGsBRwmkA4Je_gO95NT4bFa+e=PQcdV+mU9MmraOMJuBxwA@mail.gmail.com> (raw)
In-Reply-To: <A62ACF57-AC88-4B8C-ABDE-FBA0E8DD9C5D@bittext.nl>
[-- Attachment #1.1: Type: text/plain, Size: 889 bytes --]
On Fri, 14 Oct 2022 at 14:58, Taco Hoekwater via ntg-context <
ntg-context@ntg.nl> wrote:
>
>
> > On 14 Oct 2022, at 14:26, Alan Braslau via ntg-context <
> ntg-context@ntg.nl> wrote:
> >
> > Are you using MP in scaled integer or in doubleprecision mode?
> >
> > I have not looked into the MP angle operator code, but my suspicion is
> that it is based on some super-clever John Hobby scheme optimized for
> scaled integer calculations.
>
> The scaled version of “angle” is a handwritten approximation in web, not
> using
> any math library. I really doubt that that code is faster than calling
> atan2()
> on a modern machine, but I’ve kept it in because using a lib might give
> slightly
> different results.
>
iirc, in metapost the whole scaled number system has no dependency from
any external math library
(I have not checked the lmtx source yet).
[-- Attachment #1.2: Type: text/html, Size: 1335 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2022-10-14 13:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 5:40 Thangalin via ntg-context
2022-10-13 6:42 ` Max Chernoff via ntg-context
2022-10-13 19:51 ` Thangalin via ntg-context
2022-10-14 0:35 ` Max Chernoff via ntg-context
2022-10-14 8:07 ` Hans Hagen via ntg-context
2022-10-14 14:40 ` Alan Braslau via ntg-context
2022-10-14 18:59 ` Thangalin via ntg-context
2022-10-14 22:42 ` Alan Braslau via ntg-context
2022-10-14 23:09 ` Thangalin via ntg-context
2022-10-15 1:22 ` Alan Braslau via ntg-context
2022-10-14 12:26 ` Alan Braslau via ntg-context
2022-10-14 12:58 ` Taco Hoekwater via ntg-context
2022-10-14 13:05 ` luigi scarso via ntg-context [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='CAG5iGsBRwmkA4Je_gO95NT4bFa+e=PQcdV+mU9MmraOMJuBxwA@mail.gmail.com' \
--to=ntg-context@ntg.nl \
--cc=luigi.scarso@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 NNTP newsgroup(s).