Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83220
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54E60D80.8010507@lsces.co.uk>
References: <011801d04a07$83ab1c00$8b015400$@php.net>
	<CABDNdAFQsbo-A-gijPCwYDOf3ts-yKpP0tAL--WUaLU26GB-AQ@mail.gmail.com>
	<016f01d04a3a$e9183220$bb489660$@php.net>
	<CAESVnVoM7YbmXA8hTG1O66j+6YX3Xx2Q3uj_F=TPjHA4ws=8JA@mail.gmail.com>
	<d8031ce52e9965c789887e8f7b687a4e@mail.gmail.com>
	<CAESVnVpA+M6iv_zbDmKTEF8Q1zKjwnbi1ucc=UyuUyRr+X+U3w@mail.gmail.com>
	<022801d04ab1$4a0c47d0$de24d770$@php.net>
	<1913e09d7f52541901d8574d2080a63f@mail.gmail.com>
	<CAAyV7nFD=BQ5dBYiKzhbOKTomKmWvruTnb=R_n9mYB-Lz1P9pg@mail.gmail.com>
	<7a5d96b34b98ec1f3ee17be7fa6a1e81@mail.gmail.com>
	<CAPhkiZxpYbaPN1370_HFTVnBA=Jg-rU8DrB2P+2dmRcJfGWPtw@mail.gmail.com>
	<2CBDEB67-3DE3-437D-9AF3-0E6A92027244@zend.com>
	<CAPhkiZwcD3h42=9eak4uP9n2GBE=v0LVP6Ncq9Oz7L91dJ5y5w@mail.gmail.com>
	<4cc0c81c7199a452534bb8edcdb19914@mail.gmail.com>
	<54E589F6.9030002@garfieldtech.com>
	<d62afd01c97a2d00466ac88579fa861c@mail.gmail.com>
	<54E5B9DD.6080607@lsces.co.uk>
	<c2921bcfb5313c4e3fa3df24fa8381eb@mail.gmail.com>
	<54E60D80.8010507@lsces.co.uk>
Date: Thu, 19 Feb 2015 08:25:35 -0800
Message-ID: <CAEZPtU4HAC0szjSEZ_X-YDokTn+C=5Ly0Y+dm3UnYUDAQ_E3xw@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Reviving scalar type hints
From: pierre.php@gmail.com (Pierre Joye)

On Thu, Feb 19, 2015 at 8:21 AM, Lester Caine <lester@lsces.co.uk> wrote:
> On 19/02/15 12:52, Zeev Suraski wrote:
>>> Now that all made sense!
>>> >
>>> > My only grey area is 'allowing sensible ones' where the size is an
>>> > integral part
>>> > of what is 'sensible' ... the one where conventional strict typing uses a
>>> > type
>>> > of the right size?
>> I think the guiding principal for these conversions should be no data loss.
>> This may mean we have different limits on different architectures, depending
>> on whether they're 32-bit or 64-bit.
>
> This still leaves the 'black hole' caused by the fact that databases are
> actively using 'BIGINT' even on 32 bit platforms. It may be that the
> only practical approach is gmp, but using that and writing code that
> selects that on a 32bit platform, then switching to clean 64bit maths on
> a 64bit platform does not sound like simplifying things?
>
> As with other debates, some say ignore 32 bit, and others say lets loose
> the constraints altogether, but having a fundamental type behave
> differently depending on platform is a problem?


Lester,

You keep coming with this topic in every possible threads.

As I understand that DB interactions are some of the primary usages of
PHP, this discussion has nothing to do with that. DB drivers will do
what they have to do to deal with PHP & DB types, as they always do.
It would be very good if you could focus on the actual content of a
RFC or discussion instead.

-- 
Pierre

@pierrejoye | http://www.libgd.org