Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57003 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 94311 invoked from network); 22 Dec 2011 15:17:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Dec 2011 15:17:39 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.170 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.216.170 mail-qy0-f170.google.com Received: from [209.85.216.170] ([209.85.216.170:61600] helo=mail-qy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5D/33-12618-01A43FE4 for ; Thu, 22 Dec 2011 10:17:36 -0500 Received: by qcsd16 with SMTP id d16so5414877qcs.29 for ; Thu, 22 Dec 2011 07:17:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KXViG5TJuBrAEecVig7L/J6H/PVyWmxjrfXXtO42cCc=; b=RwdGgScXms7aQRo5m4S0slVdTY/vj9WoHfjCvozA4kxxrJPlITuMIVxm9a9x/BfknG aquk5JH8JyJFAA9ny1aO8897dKdBkzbNXBfUgA6Fm1F0ZaJhLovxLj0r2Zn/d6Y7rcHJ a5Ey37Fjf/qxswFEgyROsEBbIfzklYny2b31Q= MIME-Version: 1.0 Received: by 10.224.192.8 with SMTP id do8mr14101377qab.46.1324567053638; Thu, 22 Dec 2011 07:17:33 -0800 (PST) Received: by 10.229.54.140 with HTTP; Thu, 22 Dec 2011 07:17:33 -0800 (PST) In-Reply-To: References: <2095305E-D4E3-4D7E-8218-32EE99688E0C@GMAIL.COM> <2C90FB94-38C4-4270-8C6A-B89304BA8ED8@gmail.com> <159A7CA2-8561-40DA-9434-CAAE12304DDB@gmail.com> <005701ccc0b3$58c8dee0$0a5a9ca0$@alliantinternet.com> <20111222145159.GY25857@alliantinternet.com> <006101ccc0ba$46b81160$d4283420$@alliantinternet.com> Date: Thu, 22 Dec 2011 16:17:33 +0100 Message-ID: To: Keloran Cc: Dmitri Snytkine , Alain Williams , internals@lists.php.net Content-Type: multipart/alternative; boundary=20cf30050c68b69b2f04b4afccf1 Subject: Re: [PHP-DEV] Return Type Hinting for Methods RFC From: tyra3l@gmail.com (Ferenc Kovacs) --20cf30050c68b69b2f04b4afccf1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable scalar type hinting was rejected in the past multiple times. I think that expanding this RFC (against the wish of the original author of the RFC) would be a sure way to guarantee the same result for this RFC as well.. On Thu, Dec 22, 2011 at 4:08 PM, Keloran wrote: > i would love to see this expanded aswell (the way type hinting on functio= n > variables was supposed to be), so that it could be > > string, int > > e.g. > function int test(bool $tester) { > if ($tester) { return 5; } > return 99; > } > > On Thu, Dec 22, 2011 at 2:59 PM, Dmitri Snytkine < > dsnytkine@ultralogistics.com> wrote: > > > I never said to make it mandatory, only to make it available. Just like > the > > type hinting of function call is optional but not mandatory, which is a > big > > advantage over Java in my opinion. > > After all, if you make return type hinting mandatory, it would break 10= 0% > > of > > all existing php scripts. > > > > To clarify I am asking to make type hinting for variable declaration an > > available option. > > > > Dmitri Snytkine > > Web Developer > > Ultra Logistics, Inc. > > Phone: (888) 220-4640 x 2097 > > Fax: (888) 795-6642 > > E-Mail: dsnytkine@ultralogistics.com > > Web: www.ultralogistics.com > > > > "A Top 100 Logistics I.T. Provider in 2011" > > > > > > -----Original Message----- > > From: Alain Williams [mailto:addw@phcomp.co.uk] > > Sent: Thursday, December 22, 2011 9:52 AM > > To: internals@lists.php.net > > Subject: Re: [PHP-DEV] Return Type Hinting for Methods RFC > > > > On Thu, Dec 22, 2011 at 03:33:40PM +0100, Sebastian Krebs wrote: > > > > > > private \ArrayObject $customers; > > > > > > > > > > Once more "Why is PHP not Java?" > > > > That comment confuses matters. People use PHP for all sorts of reasons, > the > > desire to tighten up in some places, on some occasions, should not be > > treated > > with derision. > > > > Tighter declarations, or any declarations at all, would not be mandator= y. > > It > > would > > be something that some projects might want to do. It would be nice if > this > > could be > > done on a module but module basis ... eg the implementors of a class > > library > > might > > want to be really strict while allowing the class users to not be stric= t. > > > > Just because Java has a feature that you appear to not like, does not > mean > > that > > others might not want it in some circumstances. > > > > -- > > Alain Williams > > Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, > IT > > Lecturer. > > +44 (0) 787 668 0256 http://www.phcomp.co.uk/ > > Parliament Hill Computers Ltd. Registration Information: > > http://www.phcomp.co.uk/contact.php > > #include > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --20cf30050c68b69b2f04b4afccf1--