zsh-workers
 help / color / mirror / code / Atom feed
From: ZyX <kp-pav@yandex.ru>
To: Vincent Lefevre <vincent@vinc17.net>,
	"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Math expression evaluation error?
Date: Wed, 14 Jan 2015 02:03:33 +0300	[thread overview]
Message-ID: <2295541421190213@web9j.yandex.ru> (raw)
In-Reply-To: <20150113160031.GA12079@ypig.lip.ens-lyon.fr>

13.01.2015, 19:01, "Vincent Lefevre" <vincent@vinc17.net>:
> On 2015-01-12 19:18:22 +0300, ZyX wrote:
>>  12.01.2015, 12:18, "Vincent Lefevre" <vincent@vinc17.net>:
>>>  It's only a notation problem. Unfortunately / was chosen (historically,
>>>  not by zsh) as the symbol for integer division. The shell expression
>>>  1/2 + 1/2 just means:
>>>
>>>    integer_div(1,2) + integer_div(1,2)
>>>
>>>  where integer_div is the integer division function, which gives 0.
>>>  This is perfectly correct math.
>>  It is not integer division.
>
> In POSIX, it is always an integer division.

What?!

1. How POSIX is related? Zsh is not a POSIX shell and it is not emulation mode that is being discussed here.
2. If this standard is correct: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap01.html#tagtcjh_15 then it references ISO C standard. The ISO C standard (C99) says the following for multiplicative operators:

   > 6.5.5 Multiplicative operators
   …
   > 3 The usual arithmetic conversions are performed on the operands.
   > 2 Each of the operands shall have arithmetic type. The operands of the % operator shall
   >   have integer type.
   …
   > 5 The result of the / operator is the quotient from the division of the first operand by the
   >   second; the result of the % operator is the remainder. In both operations, if the value of
   >   the second operand is zero, the behavior is undefined.
   > 6 When integers are divided …

   Where do you see a requirement for `/` to be integer division?
3. POSIX (http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_04) says that “Only signed long integer arithmetic is required.” And the section referenced there talks about signed long or double. Signed long integer arithmetic is *required* to be in there, but signed long integer arithmetics is *not required* to be the *only* arithmetics present in POSIX shell.

So no, `/` has nothing to do with integer division, except that the referenced C standard expects well-defined integer division in case two integers are divided. If you have another POSIX standard or another interpretation please show it here.

>>  1.0/2 and 1/2.0 will give the same result: 0.5.
>
> because 1.0 and 2.0 don't have an integer type. Therefore the result is
> unspecified by POSIX, and zsh chooses to do a floating-point division.
>>  If you want to see language with operator for integer division check
>>  out Python-3: it has / for always-floating-point-unless-overridden
>>  and // for always-integral-unless-overridden
>
> For Python, but not for zsh, unfortunately. But this choice comes
> from POSIX historical behavior (and perhaps earlier).
>>  I would rather call it “type-specific division”.
>
> In zsh. In POSIX, it is *always* an integer division. There is no
> floating-point there.
>
> An alternative choice zsh could have done is to return an error
> if the / operator is used in a floating-point context, and use a
> different operator for the floating-point division. However the
> use of / for integer division could still be surprising.
>
> --
> Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


  reply	other threads:[~2015-01-13 23:15 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
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 [this message]
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=2295541421190213@web9j.yandex.ru \
    --to=kp-pav@yandex.ru \
    --cc=vincent@vinc17.net \
    --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).