9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] circular fonctions: precision?
Date: Mon,  3 Oct 2011 13:41:31 +0200	[thread overview]
Message-ID: <20111003114131.GA7326@polynum.com> (raw)
In-Reply-To: <20111002190618.54195B852@mail.bitblocks.com>

On Sun, Oct 02, 2011 at 12:06:18PM -0700, Bakul Shah wrote:
>
> > I sometimes wonder if the more common 64bits will not someday see
> > CAD or related software go back to scaled integer arithmetic =E0 la
> > Intergraph dgn, where 64bits is enough for the range of coordinates
> > and precision used...
>
> double precision seems enough for most things. ieee754-2008
> has quad precision... Symbolic math package Macsyma (& Maxima)
> has had bigfloats (arbitray precision floating point) for
> decades.  Supposedly some Common Lisp implementation have
> those as well.  Mechanical CAD packages would probably get
> more benefit from symbolic math capabilities than just scaled
> integers (keep everything in formulas until when you
> absolutely need numerical results!).

To resort to algebra (infinite precision by symbol combinations) is,
indeed, a general rule. For symbolic math capabilities, I have wandered
around the concept for geometrical description (like METAFONT/MetaPost,
where there is this distinction that is mostly blurred in programming
languages---except for basic conditionnals--- : the distinction between
an assignation and an equation).

But to come back to programming, when calculus is the crux, the more
common/known even new! programming languages are not great tools, and
"portability" i.e. proved accuracy of the implementation for a wide
range of hardware/software is fuzzy. And it's amazing to see how one can
rapidly face errors even with very basic computations. And even with
integer arithmetic, not much help is guaranteed by languages.
--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



  reply	other threads:[~2011-10-03 11:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-02 16:38 tlaronde
2011-10-02 17:52 ` Bakul Shah
2011-10-02 18:06   ` erik quanstrom
2011-10-02 18:40     ` Bakul Shah
2011-10-02 18:44       ` erik quanstrom
2011-10-02 18:59         ` andrew zerger
2011-10-02 19:04         ` tlaronde
2011-10-02 19:14         ` Bakul Shah
2011-10-02 19:18           ` erik quanstrom
2011-10-02 18:44     ` tlaronde
2011-10-02 18:48       ` tlaronde
2011-10-02 18:28   ` tlaronde
2011-10-02 19:06     ` Bakul Shah
2011-10-03 11:41       ` tlaronde [this message]
2011-10-03 14:39         ` Bakul Shah
2011-10-03 14:46           ` erik quanstrom
2011-10-03 15:29             ` Bakul Shah
2011-10-03 15:58               ` Bakul Shah
2011-10-03 16:49           ` tlaronde
2011-10-03 13:03 ` Russ Cox
2011-10-03 14:44   ` Bakul Shah
2011-10-03 14:57     ` Russ Cox
2011-10-03 15:34       ` Bakul Shah
2011-10-03 15:47         ` Russ Cox
2011-10-03 16:53   ` tlaronde

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=20111003114131.GA7326@polynum.com \
    --to=tlaronde@polynum.com \
    --cc=9fans@9fans.net \
    /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).