zsh-workers
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-workers@zsh.org
Subject: Re: Math expression evaluation error?
Date: Fri, 09 Jan 2015 14:19:51 -0800	[thread overview]
Message-ID: <54B05407.7090303@eastlink.ca> (raw)
In-Reply-To: <54B04ADA.9050102@gmail.com>

On 01/09/2015 01:40 PM, jdh wrote:
> Thanks for the detailed explanation.   I suggest that the an 
> additional line be added to the manual, which would say something like:
>
    {
    $ echo $(( 6+3/8. + 10 + 5/8  ))
    $ echo $(( 6+3/8  + 10 + 5/8. ))
    $ echo $(( 6+3/8. + 10 + 5/8. ))
    $ echo $(( 6+3/8  + 10 + 5/8  ))
    }

    16.375
    16.625
    17.
    16           << really?

    $ setopt force_float

    {
    $ echo $(( 6+3/8. + 10 + 5/8  ))
    $ echo $(( 6+3/8  + 10 + 5/8. ))
    $ echo $(( 6+3/8. + 10 + 5/8. ))
    $ echo $(( 6+3/8  + 10 + 5/8  ))
    }

    17.
    17.
    17.
    17.


Thanks for the heads up, I now know not to trust zsh math without the 
option.
I wonder tho why anyone would ever want the first set of results. 
Who/why/when
do we want bad math? Wouldn't we prefer accurate results as the default with
the option to have broken math for people who like broken math? Why not have
it work properly and that's that--nothing to explain, it just works as 
you'd expect it to work?

  6 + 3/8 + 10 + 5/8 ...
what sane calculator is going to give me '16' for that?


  reply	other threads:[~2015-01-09 22:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 19:46 jdh
2015-01-09 20:15 ` Peter Stephenson
2015-01-09 21:40   ` jdh
2015-01-09 22:19     ` Ray Andrews [this message]
2015-01-09 23:06       ` Lawrence Velázquez
2015-01-09 23:52         ` Ray Andrews
2015-01-10  0:25           ` Bart Schaefer
2015-01-10  7:27             ` Ray Andrews
2015-01-10 16:53               ` Bart Schaefer
2015-01-10 18:48                 ` Ray Andrews
2015-01-10 19:14                   ` Bart Schaefer
2015-01-10 22:21                     ` Ray Andrews
2015-01-11  1:51                       ` Bart Schaefer
2015-01-11  5:10                         ` Ray Andrews
2015-01-12  9:17                           ` Vincent Lefevre
2015-01-12 16:18                             ` ZyX
2015-01-13 16:00                               ` Vincent Lefevre
2015-01-13 23:03                                 ` ZyX
2015-01-14 14:47                                   ` Vincent Lefevre
2015-01-14 21:37                                     ` ZyX
2015-01-15 13:34                                       ` Vincent Lefevre
2015-01-15 13:41                                         ` Vincent Lefevre
2015-01-15 18:32                                         ` ZyX
2015-01-15 21:57                                           ` Bart Schaefer
2015-01-09 22:40     ` Peter Stephenson
2015-01-12 10:55       ` Peter Stephenson
2015-01-14 15:02       ` Vincent Lefevre
2015-01-14 15:38         ` Peter Stephenson
2015-01-15 14:58           ` Peter Stephenson

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=54B05407.7090303@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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