Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75631
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.192.180 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <1240076591.91249.1405564441970.open-xchange@app1.ox.registrar-servers.com>
References: <1240076591.91249.1405564441970.open-xchange@app1.ox.registrar-servers.com>
Date: Wed, 16 Jul 2014 20:23:43 -0700
Message-ID: <CAESVnVodJ03HwEAUJ3H+-3pdTxuaWf=8Q+YQokP-CW7XxnVJ1Q@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Tjerk Meesters <tjerk.meesters@gmail.com>, bishop@php.net, 
	PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] intdiv()
From: pollita@php.net (Sara Golemon)

On Wed, Jul 16, 2014 at 7:34 PM, Andrea Faulds <ajf@ajf.me> wrote:
> What are you suggesting you do for an integer division, then? ($a - ($a % $b)) /
> $ b? The division operator already returns an integer. Or should I just use
> intdiv()?
>
Wow. I just finally understood what your RFC was going for.  I thought
you were trying to cover the case where ($a%$b)==0, but you're not,
you're trying to do truncated integer division regardless of
remainder.  I also missed the fact that div_function does the right
thing already as well. My bad for emailing from the bus.

Okay, that's another animal entirely.

Do we need a new operator for that?  It feels un-php to me, and the
kind of problem bigint objects should be meant to solve.  On the other
hand, having $a/$b != $a/$b (Off by more than 100 in this instance).
But back on the first hand, that's consistent with other operations on
large floats anyway.  PHP_INT_MAX + 1 != One more than PHP_INT_MAX,
for example.

-Sara