help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: arithmetic anomaly
Date: Fri, 26 Mar 2021 08:35:47 -0700	[thread overview]
Message-ID: <691e63e8-aff6-cce6-d7b4-7bf6de10363a@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMqMe-dFWSWLnsn=K9e_gqs+-QedXU_QqOtiqeYO6cV8bg@mail.gmail.com>

On 2021-03-26 7:49 a.m., Roman Perepelitsa wrote:
> Aborted based on which condition? If the result of an operation is not 
> representable exactly in a double? If so, then even `1. / 10` would 
> abort because the real number 0.1 is not representable.
Ha!  You have a point there!  The article you linked talked about some 
of these issues, but surely in my case it's simply a plain fact that no 
decimal past 15 can be accurate ever?  Perhaps in practice this is not 
so easy to distinguish but we used to end rounding errors with that 
(what's it called?) the 'S' on it's side, the 'approximation' symbol.  
Anyway, it's easy for me to preach since I don't have to figure out how 
this would work in practice.  It's easy to talk about but perhaps not so 
easy to code.  For now I'm awake to the issue: no accuracy past 15 digits.

> Roman.

  reply	other threads:[~2021-03-26 15:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 15:52 Ray Andrews
2021-03-25 20:40 ` Lawrence Velázquez
2021-03-25 22:44   ` Ray Andrews
2021-03-25 22:54     ` Roman Perepelitsa
2021-03-25 23:57       ` Ray Andrews
2021-03-26  0:16 ` Oliver Kiddle
2021-03-26  0:37   ` Ray Andrews
2021-03-26 10:35     ` Roman Perepelitsa
2021-03-26 14:36       ` Ray Andrews
2021-03-26 14:49         ` Roman Perepelitsa
2021-03-26 15:35           ` Ray Andrews [this message]
2021-03-26 17:09             ` Lawrence Velázquez
2021-03-26 21:45               ` Ray Andrews
2021-03-26 21:59                 ` Lawrence Velázquez

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=691e63e8-aff6-cce6-d7b4-7bf6de10363a@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-users@zsh.org \


* 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.
Code repositories for project(s) associated with this public inbox


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).