From: Patrick Alken <alken@colorado.edu>
To: <gsl-discuss@sourceware.org>
Subject: Re: Multiprecision arithmetic
Date: Tue, 24 Nov 2015 16:00:00 -0000 [thread overview]
Message-ID: <565489A1.10604@colorado.edu> (raw)
In-Reply-To: <BLUPR16MB0196C8B54FECCB5A91C42236C9060@BLUPR16MB0196.namprd16.prod.outlook.com>
Yes for now I think it would add too much complexity to GSL, so we
prefer to use double precision.
Thanks for your work on the recent bugs - I haven't had a chance to look
at the patches but I'm hoping to get to this soon.
Patrick
On 11/24/2015 07:18 AM, Bill Maier wrote:
> I notice than in the write-up for bug #45746 it is suggested that multiprecision
> arithmetic be used in a portion of the calculation to produce a more precise
> result. Is this something that would be considered in GSL? I did a search
> through the code for mpfr or gmp and did not find either. In fact I couldn't find
> any code where multiprecision arithmetic is currently being used. Is it GSL
> policy to keep all internal calculations in double precision?
>
> -Bill Maier
prev parent reply other threads:[~2015-11-24 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 14:18 Bill Maier
2015-11-24 16:00 ` Patrick Alken [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=565489A1.10604@colorado.edu \
--to=alken@colorado.edu \
--cc=gsl-discuss@sourceware.org \
/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).