Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:86803 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92455 invoked from network); 23 Jun 2015 03:51:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jun 2015 03:51:39 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.169 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.192.169 mail-pd0-f169.google.com Received: from [209.85.192.169] ([209.85.192.169:33280] helo=mail-pd0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 07/DB-07834-AC7D8855 for ; Mon, 22 Jun 2015 23:51:38 -0400 Received: by pdjn11 with SMTP id n11so152215491pdj.0 for ; Mon, 22 Jun 2015 20:51:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=jYNlnDuByaVPbBOvtHOnCDfE/PuIl8EuJC4IO2h/CIY=; b=L+sIem0IIhv3vvx+sTUO8jz8nZ+tJsAzRYGAMOUq+Y4tNvlzxkgkqk/G0jQVMEKECt vpnm/Y+JvndtuiAcumWhqGAo+MDN0R16+qNU6OeaVs4v9LZ19ka9hnapyZE6MxnCg4Yx kon52l4ylytMV/TElz3ihXiIUNzSwEZ/FrZGVGA/yRmVdPZNjn3bwjA0oh+Ws/aMRrhD 6/Ze9ExICZb94cWSzCrcTFuWr3qGz13gVrJNY+ujt3Q3Sn8/6MR58HTsvT7uFenk+ZwA nVKdQQZ/s2auey4Tf4FqjRhnIeyVCj1spDrTsTELqvcchXb856IRr4c9MI3rTpNqkY7Q ZWAw== X-Received: by 10.70.43.169 with SMTP id x9mr64360452pdl.52.1435031495605; Mon, 22 Jun 2015 20:51:35 -0700 (PDT) Received: from Stas-Air.local (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48]) by mx.google.com with ESMTPSA id l7sm9852880pbq.66.2015.06.22.20.51.34 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Jun 2015 20:51:34 -0700 (PDT) Message-ID: <5588D7BF.40209@gmail.com> Date: Mon, 22 Jun 2015 20:51:27 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Rasmus Lerdorf , Dmitry Stogov CC: Bob Weinand , Anatol Belski , Kalle Sommer Nielsen , Nikita Popov , PHP internals References: <5586E5D1.4010901@lerdorf.com> <55870947.4060304@lerdorf.com> <5587334C.2080401@lerdorf.com> <55873676.6050706@gmail.com> <55876B29.90804@lerdorf.com> <55881A72.4090403@lerdorf.com> <5588477E.7050109@lerdorf.com> <5588A02C.4040602@gmail.com> <5588AEFC.1030409@lerdorf.com> In-Reply-To: <5588AEFC.1030409@lerdorf.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] hasType() for internal function parameters? From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > Is it a BC break against real code though? Fixing tests isn't a > big deal. What kind of real code would break by turning calls with > the wrong number of args from an error to a warning? Well, if we move to checking in ZPP only, then some of the errors that previously were fatals (like iterator_array("")) would now become warnings. In fact, even type mismatch is a warning for ZPP, which may be unexpected, as it was a fatal before, so we may want to change that. But in some situation, like argument number mismatch, we will have a warning, where before it was a fatal error. Which isn't strictly BC break but allows some code to pass which previously didn't and may hide some bugs. So we may want to be careful there. -- Stas Malyshev smalyshev@gmail.com