Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:77694 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67526 invoked from network); 29 Sep 2014 08:29:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Sep 2014 08:29:39 -0000 Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 198.187.29.245 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 198.187.29.245 imap11-3.ox.privateemail.com Received: from [198.187.29.245] ([198.187.29.245:48007] helo=imap11-3.ox.privateemail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 21/00-01892-17819245 for ; Mon, 29 Sep 2014 04:29:38 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id 122938800EF; Mon, 29 Sep 2014 04:29:35 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap11.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap11.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ooSty4GpioSD; Mon, 29 Sep 2014 04:29:34 -0400 (EDT) Received: from oa-edu-171-139.wireless.abdn.ac.uk (oa-edu-171-139.wireless.abdn.ac.uk [137.50.171.139]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id 34D558800DB; Mon, 29 Sep 2014 04:29:31 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) In-Reply-To: <5428B173.8030905@sugarcrm.com> Date: Mon, 29 Sep 2014 09:29:29 +0100 Cc: Dmitry Stogov , Rowan Collins , "internals@lists.php.net" Content-Transfer-Encoding: quoted-printable Message-ID: <0F4F4456-FAED-469A-8BEF-8367127DA0B1@ajf.me> References: <07153B91-E12F-4B16-ADD7-86CFC75C4642@ajf.me> <54220EB4.60001@sugarcrm.com> <6A21F4EF-476E-476C-A64B-246B8929172B@ajf.me> <5422DD87.80109@gmail.com> <568C0F03-B23B-43FC-963D-6D0D23405E9D@ajf.me> <54230209.2050406@sugarcrm.com> <54233C70.3060604@gmail.com> <54236D16.3070401@sugarcrm.com> <54242A0C.3000309@gmail.com> <5428B173.8030905@sugarcrm.com> To: Stas Malyshev X-Mailer: Apple Mail (2.1878.6) Subject: Re: [PHP-DEV] [RFC] ZPP Failure On Overflow From: ajf@ajf.me (Andrea Faulds) On 29 Sep 2014, at 02:10, Stas Malyshev wrote: > Hi! >=20 >> May be this overflow checks should be optional? >> In old ages compilers for Wirth family languages had option to enable = or >> disable overflow checks. >> If option is enabled we may throw an exception, if no - work as = today. >> Any user would be able to chose between compatibility and safety. >=20 > Given that we have l and L in parameter parsing API, it is essentially > optional, but the choice is on internals developer. I'm not sure = having > it as ini value would be the best idea, since behavior-modifying = options > in the past proved more trouble than they're worth - one more = dimension > one has to test against. This patch preserves the cap-and-not-error behaviour for L, though NaN = would continue to error. If there=92s a need for it, a new wrap-and-not-error character could be = added, basically to match what l currently does. -- Andrea Faulds http://ajf.me/