From: Henri Menke <henrimenke@gmail.com>
To: "ntg-context@ntg.nl >> mailing list for ConTeXt users"
<ntg-context@ntg.nl>
Subject: Re: graphics
Date: Thu, 13 Dec 2018 12:56:41 +1300 [thread overview]
Message-ID: <98bf5807-6a5c-53bc-36e0-11a70af8f3a3@gmail.com> (raw)
In-Reply-To: <20181212143952.3da52002@zoo>
On 13/12/18 10:39 AM, Alan Braslau wrote:
> On Thu, 13 Dec 2018 10:03:40 +1300
> Henri Menke <henrimenke@gmail.com> wrote:
>
>> Sorry, my mistake, the Bessel functions are not a GCC extension but
>> POSIX standard functions.
>> http://pubs.opengroup.org/onlinepubs/9699919799/functions/j0.html
>> Since TeX Live is always built on a POSIX platform (MSYS2 on Windows),
>> you can expect j0 etc. to be available in LuaTeX.
>
> That is true for the Bessel functions, but not for some other "-lmath"
> functions (such as the erf), so they may depend on the system.
erf definitely does not depend on the system. That is part of the C
Standard library.
https://en.cppreference.com/w/c/numeric/math/erf
But in general you are right. The zoo of special functions in the
Standard library and POSIX is rather limited. Personally I prefer using
the GNU Scientific library if I need special functions.
https://www.gnu.org/software/gsl/doc/html/index.html
Earlier this year I wrote a TUGboat article about using GSL with FFI in
LuaTeX.
https://tug.org/TUGboat/tb39-1/tb121menke-ffi.pdf
I also plan on submitting an abstract about that topic for TUG2019 in
Palo Alto.
>
> Alan
>
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-12-12 23:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 17:03 graphics Hans Hagen
2018-12-04 18:54 ` graphics Alan Braslau
2018-12-05 9:02 ` graphics Taco Hoekwater
2018-12-05 12:59 ` graphics Hans Hagen
2018-12-05 15:24 ` graphics Alan Braslau
2018-12-06 7:31 ` graphics Procházka Lukáš Ing.
2018-12-05 9:14 ` graphics Henri Menke
2018-12-05 9:22 ` graphics luigi scarso
2018-12-05 12:37 ` graphics Hans Hagen
2018-12-05 12:55 ` graphics luigi scarso
2018-12-07 8:06 ` graphics Mikael P. Sundqvist
2018-12-07 12:20 ` graphics luigi scarso
2018-12-07 15:15 ` graphics Alan Braslau
2018-12-08 8:31 ` graphics Mikael P. Sundqvist
2018-12-08 15:15 ` graphics Alan Braslau
2018-12-12 19:42 ` graphics Mikael P. Sundqvist
2018-12-12 19:56 ` graphics Alan Braslau
2018-12-12 20:02 ` graphics Henri Menke
2018-12-12 20:12 ` graphics Alan Braslau
2018-12-12 21:03 ` graphics Henri Menke
2018-12-12 21:39 ` graphics Alan Braslau
2018-12-12 23:56 ` Henri Menke [this message]
2018-12-12 20:13 ` graphics Mikael P. Sundqvist
2018-12-13 13:32 ` graphics Otared Kavian
2018-12-13 15:44 ` graphics Alan Braslau
2018-12-13 16:07 ` graphics luigi scarso
2018-12-13 20:33 ` graphics Henri Menke
2018-12-12 13:51 ` graphics Mathias Schickel
2018-12-12 18:36 ` graphics Alan Braslau
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=98bf5807-6a5c-53bc-36e0-11a70af8f3a3@gmail.com \
--to=henrimenke@gmail.com \
--cc=ntg-context@ntg.nl \
/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).