Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86065
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAGa2bXY9Z2YTT-rp5qCzE_jwaW1F0COE_j6sEjHXBECXmdwdTw@mail.gmail.com>
References: <CAGa2bXYzp3XimLXxC+Py2t1DWhCfX8coTdYHzf6zEiKdxA7r8Q@mail.gmail.com>
	<55401F31.9030703@gmail.com>
	<CAObuZduZBM0GyWJMA1Fd7eCgPE4vFFZrrhpREQ50a4QJhG6Nvg@mail.gmail.com>
	<CAGa2bXar_oXrsPAErNx5BUdkFAy-p8-D0tfhc3pAnDTGBGJJ7Q@mail.gmail.com>
	<55416849.9010808@gmail.com>
	<CAGa2bXbkCx2Nqb9YBut3id4N=nhjLBGPN8Ucrx7R6mRnGjB2og@mail.gmail.com>
	<554176D6.2030007@gmx.de>
	<CAGa2bXaPjvkFYtkhRM1JisSvxgR0v8adkD_P_zkUng4xfBWFHg@mail.gmail.com>
	<55418CBE.6050609@gmail.com>
	<CAGa2bXZAY_9qx9D+K11ApJH9DKzTvxze+=E5=rVhQj_OaGfxGQ@mail.gmail.com>
	<CAGa2bXbYDAzsqA2PqqngtNTpjN2Oq9-q4BNRjxtU85LJ+WMExg@mail.gmail.com>
	<CAMPTd_DhriS6JdCdVWfd8o+o1Dc_UC+AR=nASSoVu+trzLJn_w@mail.gmail.com>
	<CAGa2bXY9Z2YTT-rp5qCzE_jwaW1F0COE_j6sEjHXBECXmdwdTw@mail.gmail.com>
Date: Wed, 29 Apr 2015 21:49:55 -0700
Message-ID: <CAMPTd_C3nv6Vxyou-UA9n9n+3RZuG2qPqRrRFdOorNZQkbQzEw@mail.gmail.com>
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e01493afabb8a720514e9d3e6
Subject: Re: [PHP-DEV] Adding "numeric" type hint
From: walterp@gmail.com (Walter Parker)

--089e01493afabb8a720514e9d3e6
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 29, 2015 at 9:33 PM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:

> Hi Walter,
>
> On Thu, Apr 30, 2015 at 11:52 AM, Walter Parker <walterp@gmail.com> wrote:
>
>> Are you asking to have both the 32 and 64 bit versions of PHP fully map
>> to the type system in SQLite? The type system in SQLite appears to have
>> been setup to map to programming language that lots of types (modern C,
>> C++, maybe Java) rather than PHP.
>>
>> I think you might have an easier time fixing the SQLite adaptor for PHP
>> than making both 32 and 64 bit PHP map to the type structure for SQLite
>> completely transparently with full type defs.
>>
>
> It's not a SQLite/etc access library issue, but the user code issue.
>
> Average PHP users will use int type hint for record IDs. This results in
> fatal
> error (or exception). These code does not have to be my/your code, but
> other libraries written by someone else.
>
> Regards,
>
> --
> Yasuo Ohgaki
> yohgaki@ohgaki.net
>


Then this is exactly why we need type hints. If the average user is using
32 ints to map to 64 bit values, then someone has written broken code. The
code should fail with a type check error, not be automagically fixed if you
are using types. At some point the programmer should take responsibility
for matching the DB API to the code base. Hiding mistakes only sets up the
uninformed users for mistakes later.

Mixing 32 bit code/sizes with 64 code/sizes requires that you pay some
attention to sizes. Do everything in 32 bit, not a problem. Do everything
in 64 bit, not a problem. Mix the two and there is a cost. As far as a I
can tell, they is little desire in the current day to make the 32/64 hybrid
modes easier/simpler. This is a fact that people will have live with (or do
the work themselves). I see it as a legacy issue that is becoming more and
more irrelevant.

It would be nice to help, but it may setup future legacy issues that we
would rather not support.


Walter

-- 
The greatest dangers to liberty lurk in insidious encroachment by men of
zeal, well-meaning but without understanding.   -- Justice Louis D. Brandeis

--089e01493afabb8a720514e9d3e6--