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 23:27:13 -0800	[thread overview]
Message-ID: <54B0D451.1000502@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7Yq40Ksd-Y49hoBLexS+-o-CQHjtZ34k5zksY+g6W0=cg@mail.gmail.com>

On 01/09/2015 04:25 PM, Bart Schaefer wrote:
> On Fri, Jan 9, 2015 at 3:52 PM, Ray Andrews <rayandrews@eastlink.ca> wrote:
>> It seems to me that if the
>> shell accepts the fractions then it should return the correct answer.  I'd
>> make integer math  the option and have accurate results as the default
>> but that's just me.
>
> 3/8 is not a fraction.  Yes, in a text paragraph like this one I might
> write 3/8 as a fraction because I can't write a superscript three over
> a subscript eight, but in an arithmetic expression 0.375 is a fraction
> and 3/8 is "integer 3 divided by integer 8", and the definition of
> "divided by" includes "if both numerator and denominator are integers,
> then the result must also be an integer".  As has been mentioned, this
> is the way a LOT of programming languages work.
Well, this is one of those things that won't change, but I must say that 
in my experience an overwhelming majority of people would say that 3/8 
is a fraction, and they would be surprised that in zsh, by default :

1/2 + 1/2 = 0

And I'll bet they'd wonder why even though zsh is quite capable of doing 
floating point math, it chooses to behave like an abacus by default, 
other programing languages notwithstanding.  Never mind, I'll just 
'setopt force_float' and have accuracy.   I'm glad I was forewarned 
about this, however.
>


  reply	other threads:[~2015-01-10  7:27 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
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 [this message]
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=54B0D451.1000502@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).