Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:77219 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51251 invoked from network); 15 Sep 2014 11:49:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Sep 2014 11:49:08 -0000 Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.52 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.52 mail-wg0-f52.google.com Received: from [74.125.82.52] ([74.125.82.52:62205] helo=mail-wg0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FC/7C-64534-432D6145 for ; Mon, 15 Sep 2014 07:49:08 -0400 Received: by mail-wg0-f52.google.com with SMTP id x13so3685162wgg.11 for ; Mon, 15 Sep 2014 04:49:01 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=dJMxcw0W2GTxPwkptWUfJDsdny4OJyP0XQYmhsdPP7Y=; b=TdREK9/16m/esMeRNRqnkJNlenXezn+gN83R6eRyGFOODxvmnccHWSbSSvANDWf8Tw jlkhYgMJcvieX0s44/jDH1Qn4SsMCwaESv3IN6gtJAULtOOC0FkUhcQMdetcwAgHaTgR r7I1IY68lgxR10yZ81qYVWFuWb/D/02llZLXT8CxpcI/t99NP+HLR8j09rB+0rt7JY8V 6/V7NKJk3fqPMIDXoCBt63weieYNt9wxpUQ9mcTqfuMBcFe8ByVpAfjApQ3ZuAjGhjPV Vgk0C5lX2THyBkK1h6Wbb1cCRhEcmgMKRS4/SVTiSwm5KdFwc6/lJd84C/eprFI0f9RD 2F/A== X-Received: by 10.194.92.42 with SMTP id cj10mr2755904wjb.113.1410781741186; Mon, 15 Sep 2014 04:49:01 -0700 (PDT) Received: from [192.168.0.177] ([62.189.198.114]) by mx.google.com with ESMTPSA id ll20sm11406457wic.14.2014.09.15.04.48.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Sep 2014 04:49:00 -0700 (PDT) Message-ID: <5416D224.10709@gmail.com> Date: Mon, 15 Sep 2014 12:48:52 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: PHP internals References: <6893A97A-EC4C-4124-B804-96E2A26B953F@ajf.me> <20140914000718.GB14312@phcomp.co.uk> <3177B936-50C1-4E5D-8687-FD235C72B411@ajf.me> <54153692.7050500@sugarcrm.com> <9CE963B0-E624-4267-BC2A-0F8D1F985DAE@ajf.me> <6f2236e18c61d30b247e1c6bb2de10f1@mail.gmail.com> <8556C1E7-EDF3-47E2-9DA0-C9AB63DE56E6@ajf.me> <6E402FE8-119A-4BBB-B652-97A0DBEC8BC9@ajf.me> <5415DC76.7070105@gmail.com> <54167CDC.9040801@sugarcrm.com> In-Reply-To: <54167CDC.9040801@sugarcrm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [VOTE][RFC] Scalar Type Hinting with Cast From: rowan.collins@gmail.com (Rowan Collins) Stas Malyshev wrote (on 15/09/2014): > It's not the issue here. Nobody wants 100% of functions to do the same, > and everybody knows there will be exceptions when some functions can not > accept all values covered by type, or can accept multiple types but only > in certain situations, etc. etc. What we want is to have one set of > rules (yes, again, not covering 100% of functions, both user and > internal, but covering most of them in the same way) instead of two > different sets of rules. I agree that 100% is an unrealistic goal, but I don't think I've yet seen someone actually point at a documented set of rules that even 80% of current functions follow. I guess there is a default/normal usage of ZPP etc that most internal functions use, but I have yet to find the documentation on what this actually is (README.PARAMETER_PARSING_API lists the C types you have to use, but not the PHP types & values that can be provided by the user, or what happens if they don't). Apologies if I'm missing something obvious here. Regards, -- Rowan Collins [IMSoP]