Computer Old Farts Forum
 help / color / mirror / Atom feed
From: peter at rulingia.com (Peter Jeremy)
Subject: [COFF] Fwd: Old and Tradition was [TUHS] V9 shell
Date: Thu, 13 Feb 2020 17:57:20 +1100	[thread overview]
Message-ID: <20200213065720.GA79914@server.rulingia.com> (raw)
In-Reply-To: <CANCZdfoxPy3LQvQ-_bAcj1wPKhHbrTvs9qAsXtpTdVHSTCZZDw@mail.gmail.com>

On 2020-Feb-12 15:11:27 -0700, Warner Losh <imp at bsdimp.com> wrote:
>Most cs types barely know that 2.234 might not be an exact number when
>converted to binary...

My favourite example (based on a real bug that I was involved in
investigating) is: int(0.29 * 100) = 28 (using IEEE doubles).  That result
is very counter-intuitive.  (Detailed explanation available on request).

In some ways IEEE-754 has made things worse - before that standard, almost
every computer system implemented something different.  Floating point was
well known to be "here be dragons" territory and people who ventured there
were either foolhardy or had enough numerical analysis training to be able
to understand (and cope with) what the computer was doing.

IEEE-754 offered a seeming nirvana - where the same inputs would result in
the same outputs (down to the bit) irrespective of what computer you ran
your code on.  The underlying problems were still present but, at least in
simple cases, were masked.  Why employ an experienced numerical analyst to
develop the code when a high-school student can translate the mathematical
equations into running code in the language-du-jour?  (And some languages,
like Java, make a virtue out of hiding all the information needed to
properly handle exceptional conditions).

-- 
Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200213/42456332/attachment.sig>


  parent reply	other threads:[~2020-02-13  6:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 18:41 [COFF] " clemc
     [not found] ` <CAP2nic2C4-m_Epcx7rbW2ssbS850ZFiLKiL+hg1Wxbcwoaa1vQ@mail.gmail.com>
2020-02-12  0:57   ` [COFF] Fwd: " athornton
2020-02-12  1:58     ` clemc
2020-02-12  3:01       ` lm
2020-02-12 18:12         ` clemc
2020-02-12 21:55           ` cym224
2020-02-12 22:11           ` imp
2020-02-12 22:45             ` sauer
2020-02-12 23:05               ` lm
2020-02-12 23:54                 ` [COFF] floating point (Re: " bakul
2020-02-12 23:56                   ` bakul
2020-02-13  1:21                   ` toby
2020-02-13  6:57             ` peter [this message]
2020-02-16 21:47           ` [COFF] Fwd: " wobblygong
2020-02-16 22:10             ` clemc
2020-02-16 22:45               ` krewat
2020-02-16 23:50               ` bakul
2020-02-18  0:17                 ` dave
2020-02-18 12:48                   ` jpl.jpl
2020-02-24  9:40         ` ik
2020-02-24 15:19           ` lm
     [not found]             ` <CAP2nic0fK+=eh=5MuY4BJH6zx4tCRMWcazmm1khYMzNmEdf8ug@mail.gmail.com>
2020-02-24 16:15               ` [COFF] [TUHS] Fwd: Old and Tradition was " clemc
2020-02-24 16:19                 ` clemc
2020-02-24 16:27             ` [COFF] Fwd: Old and Tradition was [TUHS] " clemc
2020-02-12 16:28 jnc
2020-02-12 18:13 ` clemc

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=20200213065720.GA79914@server.rulingia.com \
    --to=coff@minnie.tuhs.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 NNTP newsgroup(s).