Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67624 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88583 invoked from network); 4 Jun 2013 09:59:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jun 2013 09:59:37 -0000 Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 config.schlueters.de Received: from [217.114.211.66] ([217.114.211.66:52314] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 88/4F-21406-78ABDA15 for ; Tue, 04 Jun 2013 05:59:37 -0400 Received: from [192.168.2.20] (host-188-174-221-231.customer.m-online.net [188.174.221.231]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id 33FF365CA3; Tue, 4 Jun 2013 11:59:33 +0200 (CEST) To: ivan.enderlin@hoa-project.net Cc: internals@lists.php.net In-Reply-To: <51ADA82F.6040407@hoa-project.net> References: <3e1b2d12-97cd-4928-b526-0a4b9d443ca5@email.android.com> <51ADA82F.6040407@hoa-project.net> Content-Type: text/plain; charset="UTF-8" Date: Tue, 04 Jun 2013 12:01:21 +0200 Message-ID: <1370340081.2630.108.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] 5.NEXT Integer and String type modifications From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Tue, 2013-06-04 at 10:41 +0200, Ivan Enderlin @ Hoa wrote: > > 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 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 spending 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]. To some degree, but there are enough cases which are technically and such correct but logically wrong, so the code still has to be reviewed. johannes