Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75657
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.199 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
In-Reply-To: <53C7789F.40000@sugarcrm.com>
Date: Thu, 17 Jul 2014 08:41:55 +0100
Cc: Zeev Suraski <zeev@zend.com>,
 "bishop@php.net" <bishop@php.net>,
 PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <9C4EFD88-2BD4-445A-A573-E818DC9F55CC@ajf.me>
References: <7646A8D1-69A2-4255-B048-D3B9F28B422F@ajf.me> <CAEYWF=4pxA5vE0eBEbi1Fkh7k7uqZk0rAS77oWxzPdicnTN+gQ@mail.gmail.com> <A8E995FC-7F3A-451F-8787-6566CCAE39B5@ajf.me> <CAEYWF=7YReKc9iKOnFHSWHmYKw1a5y2BU_=Hc5HBbMqdkPTMRg@mail.gmail.com> <37F89E54-C5B9-4E81-9D1B-660190BDB1FF@ajf.me> <d373a9bdc62a05dcbe2f911c2f83e2cc@mail.gmail.com> <9F08728B-AF74-4098-8D1D-BC21AB821168@ajf.me> <53C7789F.40000@sugarcrm.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Subject: Re: [PHP-DEV] [RFC] intdiv()
From: ajf@ajf.me (Andrea Faulds)


On 17 Jul 2014, at 08:17, Stas Malyshev <smalyshev@sugarcrm.com> wrote:

> Hi!
>=20
>> * Time (actually pretty common in web apps, though we have a DateTime
>> class)
>=20
> Admittedly, we're getting closer to the dreaded year 2038, but what =
does
> it actually mean to divide current Unix timestamp by 3 and why one =
would
> ever want to do this? We also have classes for real datetime =
calculations.

To divide by three is probably a bad example, but it=92s fair to point =
out that anything with UNIX timestamps would work fine with just floats =
as we don=92t need 53 bits yet.

> Here you are onto something, but how often you paginate data sets of
> MAXINT size and need exact number of pages?

Rarely, I suspect, but it would still be nice to have a proper way of =
doing the division

> If you're using ints for currency, you're probably doing it wrong. If
> you're dividing currency using integer division, I don't even know =
what
> you are trying to do, except reenacting Office Space :)

A lot of people use ints as a poor man=92s fixnum, and sometimes that=92s =
actually the right way to implement them. IIRC, Bitcoin is implemented =
using 64-bit integers internally.

> You mean image processing? If 53 bit precision is not enough there, =
I'm
> not even sure PHP should be doing that.

True, but again, you should still ask why PHP doesn=92t support integer =
division in the first place.

> IMHO this is not enough for a new operator... Especially if this means
> we have to tolerate something like %/.

%/ and %% are hardly the nicest operators, no. Myself I like %% as % =
being one part and %% being the other part of an integer division makes =
sense to me, but I can see why others might not like it.

--
Andrea Faulds
http://ajf.me/