Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57991 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 58552 invoked from network); 23 Feb 2012 23:13:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Feb 2012 23:13:30 -0000 Authentication-Results: pb1.pair.com header.from=keisial@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=keisial@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender) X-PHP-List-Original-Sender: keisial@gmail.com X-Host-Fingerprint: 74.125.82.170 mail-we0-f170.google.com Received: from [74.125.82.170] ([74.125.82.170:33548] helo=mail-we0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B6/5B-18992-918C64F4 for ; Thu, 23 Feb 2012 18:13:30 -0500 Received: by werm1 with SMTP id m1so1289672wer.29 for ; Thu, 23 Feb 2012 15:13:26 -0800 (PST) Received-SPF: pass (google.com: domain of keisial@gmail.com designates 10.180.86.230 as permitted sender) client-ip=10.180.86.230; Authentication-Results: mr.google.com; spf=pass (google.com: domain of keisial@gmail.com designates 10.180.86.230 as permitted sender) smtp.mail=keisial@gmail.com; dkim=pass header.i=keisial@gmail.com Received: from mr.google.com ([10.180.86.230]) by 10.180.86.230 with SMTP id s6mr774858wiz.16.1330038806990 (num_hops = 1); Thu, 23 Feb 2012 15:13:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=+lnFbvpPx1iLfPEqE788RXT2AjPNTbeC8axWf+Jcn/0=; b=ARY4ydSGqJCjTpTSMAAtmKrf/ghJ8I+tLgnRk6PvLLaXt6gxEL7roDEL4D2BUDXqnr xnYIJdKlo9HMeqzaWQsDQzGzAkgHBg/IcMey08Zn1HcgSlM27vQqdKU50tEOSetgKuAE kJDP54RapqH/zN0MQDOuElV3HpZQ9gUxf/FZM= Received: by 10.180.86.230 with SMTP id s6mr619174wiz.16.1330038806949; Thu, 23 Feb 2012 15:13:26 -0800 (PST) Received: from [192.168.1.26] (149.Red-83-44-158.dynamicIP.rima-tde.net. [83.44.158.149]) by mx.google.com with ESMTPS id er8sm13364318wib.1.2012.02.23.15.13.24 (version=SSLv3 cipher=OTHER); Thu, 23 Feb 2012 15:13:26 -0800 (PST) Message-ID: <4F46C93A.1010108@gmail.com> Date: Fri, 24 Feb 2012 00:18:18 +0100 User-Agent: Thunderbird MIME-Version: 1.0 To: Kris Craig CC: John LeSueur , Stas Malyshev , Anthony Ferrara , Dmitri Snytkine , Sebastian Krebs , PHP internals list References: <4F455C96.50706@gmail.com> <4F455E91.2060408@alliantinternet.com> <028001ccf1ab$0b200050$216000f0$@alliantinternet.com> <4F457517.7050901@alliantinternet.com> <028d01ccf230$91d79b00$b586d100$@alliantinternet.com> <4F4686C6.2040207@sugarcrm.com> <4F46BE01.7030007@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Enum proposal (yet another) From: keisial@gmail.com (=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=) On 23/02/12 23:49, Kris Craig wrote: > Yeah I agree, that was one of the things I listed under > "disadvantages" lol. > > I guess my question is: Does this constitute a prohibitive problem, > or is it something that we can stomach? > > I mean, if you think about it, that's really what we're talking about > anyway, right? After all, when you're writing any application, you're > either going to be writing it with strict typing or you're going to be > writing it with dynamic typing. The only difference here is that > coders with either preference will both find PHP accommodating to > their style. > > > Similarly, a somewhat weaker argument could be made that, in PHP 5, > you're either coding for procedural design or for OO design > (technically you could do both, but I wouldn't wanna touch that > codebase with a ten foot poll lol). The only difference here is that > there would be a config setting to tell the interpreter which is which. > > --Kris I think you would get developers coding for strict, and hostings set to weak. Makes more sense to have it as a per file / per function attribute, so the author can choose if they want the values passed to it to be coerced or act as if they were doing a manual check and throwing an exception.