Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67625 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90317 invoked from network); 4 Jun 2013 10:08:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jun 2013 10:08:14 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.172 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.217.172 mail-lb0-f172.google.com Received: from [209.85.217.172] ([209.85.217.172:49166] helo=mail-lb0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4F/9F-21406-C8CBDA15 for ; Tue, 04 Jun 2013 06:08:13 -0400 Received: by mail-lb0-f172.google.com with SMTP id p10so451527lbi.3 for ; Tue, 04 Jun 2013 03:08:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=rR4WDyhN0LNsXX8lvCkbAjl2AnjaY2Z5QA+FQwM1yIc=; b=Sczf0BnS/dp7uZIWW7H29AjB8/01a3AMngFttJ40cx9K0gPN/ot4L5JhlO/YpAYLYw Q3dRoKiJaZuUfSCC4mSeUq/izAKqMNy81nXOHu8lowyOdtNHpF5Gys4XoO1ONjvkEhS+ pUFwD94UhvQ38hfqJ/OD1OHR+PoH3cCYm8TnodU5a4+rFcNjObXU8hDkKB750rdCRFqS TKfggFSM5tx1jkwsQsjV88GYBuNxP39Xif+cRlfvLqWsFUcQ9fBj8qMZ3PE6F6sdu+o/ gCeelVj5z5OHtlmsqf6nC9ZmIDQKzhxREJxRwW6fIvypNIlKvUuRgsvYQWn4JS4RV3wQ KBZw== MIME-Version: 1.0 X-Received: by 10.112.151.8 with SMTP id um8mr6206580lbb.87.1370340489484; Tue, 04 Jun 2013 03:08:09 -0700 (PDT) Received: by 10.112.138.135 with HTTP; Tue, 4 Jun 2013 03:08:09 -0700 (PDT) In-Reply-To: <51ADA82F.6040407@hoa-project.net> References: <3e1b2d12-97cd-4928-b526-0a4b9d443ca5@email.android.com> <51ADA82F.6040407@hoa-project.net> Date: Tue, 4 Jun 2013 12:08:09 +0200 Message-ID: To: ivan.enderlin@hoa-project.net Cc: PHP internals Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] 5.NEXT Integer and String type modifications From: pierre.php@gmail.com (Pierre Joye) On Tue, Jun 4, 2013 at 10:41 AM, Ivan Enderlin @ Hoa 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 for >>> non-legacy code (as both would still be using native data types)... >> >> History shows that such gigantic patches are often not finished and done >> as people underestimate the size of PHP and the fact that all etensions = have >> to be checked which for this case means checking each external lib for t= heir >> 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 spend= ing >> 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 th= ink > 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. -- Pierre @pierrejoye | http://www.libgd.org