Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67628
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain hoa-project.net from 95.130.12.24 cause and error)
Message-ID: <51ADEAA7.9080309@hoa-project.net>
Date: Tue, 04 Jun 2013 15:24:55 +0200
Reply-To: ivan.enderlin@hoa-project.net
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0a2
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAAyV7nG126YkpOF-EShHbf=4rgX7gQ2VE0ShRh0-50_Yr--h4g@mail.gmail.com>	<3e1b2d12-97cd-4928-b526-0a4b9d443ca5@email.android.com>	<51ADA82F.6040407@hoa-project.net> <CAEZPtU6_oBUL_5nzV5+KSJ9R+mpUBDwVXiRk1i2AkNrFGBGV_g@mail.gmail.com>
In-Reply-To: <CAEZPtU6_oBUL_5nzV5+KSJ9R+mpUBDwVXiRk1i2AkNrFGBGV_g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] 5.NEXT Integer and String type modifications
From: ivan.enderlin@hoa-project.net ("Ivan Enderlin @ Hoa")


On 04/06/13 12:08, Pierre Joye wrote:
> On Tue, Jun 4, 2013 at 10:41 AM, Ivan Enderlin @ Hoa
> <ivan.enderlin@hoa-project.net> wrote:
>> Hey :-),
>>
>>
>> On 02/06/13 08:52, Johannes Schl=FCter wrote:
>>>> It would be a *gigantic* patch, but the userland effects should be
>>>> minimal (the only changes would be supporting longer strings, and
>>>> consistent 64
>>>> bit int support). The performance considerations should be minimal f=
or
>>>> non-legacy code (as both would still be using native data types)...
>>> History shows that such gigantic patches are often not finished and d=
one
>>> as people underestimate the size of PHP and the fact that all etensio=
ns have
>>> to be checked which for this case means checking each external lib fo=
r their
>>> correct type for all their functions etc ... but I don't wan to stop =
you,
>>> I'm happy if you do this :-) (while I'm also happy about everybody sp=
ending
>>> time on fixing bugs instead of adding such high-risk changes  ;-))
>> Is it possible to use a static C analyzer here? It could help a lot. I=
 think
>> about Frama-C [1], Pork [2] (now included in Oink [3]) or Clang Static=

>> Analyser [4] to name a few. A more complete list can be found in [5].
> We do it using Visual C++ static analyzer, which is an excellent tool
> for this kind of issue, almost on all commits. As soon as we have a
> fork for these changes I will add it so we can get regular updates.
Excellent!

--=20
Ivan Enderlin
Developer of Hoa
http://hoa-project.net/

PhD. student at DISC/Femto-ST (Vesontio) and INRIA (Cassis)
http://disc.univ-fcomte.fr/ and http://www.inria.fr/

Member of HTML and WebApps Working Group of W3C
http://w3.org/