Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50651 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21319 invoked from network); 28 Nov 2010 11:18:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Nov 2010 11:18:01 -0000 Authentication-Results: pb1.pair.com header.from=glopes@nebm.ist.utl.pt; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=glopes@nebm.ist.utl.pt; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain nebm.ist.utl.pt from 193.136.128.22 cause and error) X-PHP-List-Original-Sender: glopes@nebm.ist.utl.pt X-Host-Fingerprint: 193.136.128.22 smtp2.ist.utl.pt Linux 2.6 Received: from [193.136.128.22] ([193.136.128.22:50127] helo=smtp2.ist.utl.pt) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 93/D0-16104-66A32FC4 for ; Sun, 28 Nov 2010 06:17:59 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp2.ist.utl.pt (Postfix) with ESMTP id 5203970003C7 for ; Sun, 28 Nov 2010 11:17:55 +0000 (WET) X-Virus-Scanned: by amavisd-new-2.6.4 (20090625) (Debian) at ist.utl.pt Received: from smtp2.ist.utl.pt ([127.0.0.1]) by localhost (smtp2.ist.utl.pt [127.0.0.1]) (amavisd-new, port 10025) with LMTP id FJftsagBz-Nd for ; Sun, 28 Nov 2010 11:17:55 +0000 (WET) Received: from mail2.ist.utl.pt (mail.ist.utl.pt [IPv6:2001:690:2100:1::8]) by smtp2.ist.utl.pt (Postfix) with ESMTP id 11BB9700045F for ; Sun, 28 Nov 2010 11:17:55 +0000 (WET) Received: from cataphract (cataphract.lo.geleia.net [IPv6:2001:470:94a2:1:b488:8610:90e4:7835]) (Authenticated sender: ist155741) by mail2.ist.utl.pt (Postfix) with ESMTPSA id 322012001A31 for ; Sun, 28 Nov 2010 11:17:54 +0000 (WET) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: internals@lists.php.net References: <1290879624.7033.826.camel@guybrush> <61577946-B04E-4218-82A0-5157ADC96102@roshambo.org> <4CF231F8.5090104@sugarcrm.com> Date: Sun, 28 Nov 2010 11:14:28 -0000 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Organization: =?utf-8?Q?N=C3=BAcleo_de_Eng=2E_Biom=C3=A9di?= =?utf-8?Q?ca_do_IST?= Message-ID: In-Reply-To: <4CF231F8.5090104@sugarcrm.com> User-Agent: Opera Mail/10.63 (Win32) Subject: Re: [PHP-DEV] RFC: Making T_FUNCTION optional in method declarations From: glopes@nebm.ist.utl.pt ("Gustavo Lopes") On Sun, 28 Nov 2010 10:42:00 -0000, Stas Malyshev wrote: > Hi! > >> Sorry for moving offtopic, but if the PHP syntax is going to change >> then we should revisit other proposals that add/change syntax. For >> example, I think the short syntax for arrays was declined [from 5.3] >> mainly because it introduced a new syntax at a time we wanted to >> preserve BC: > > I find it fascinating that a short time ago the short array > syntax and other like proposals were unanimously rejected with "PHP > needs no syntax sugar, everything should be explicit and verbose!" and > now it's complete reversal - everybody supports syntax sugar, adding new > complex syntax and what not. In my opinion, the short array syntax is a completely different matter and we shouldn't be constantly diverting discussions... > > I personally am not sure this thing is worth doing, I never had a > problem with typing "function" but if so many people do, maybe it's OK > for a major version release. It's a completely redundant keyword, which I frequently forget and where I find no expressive power. But I also write a lot of Java, so I might be biased. I'm +0 on this. -- Gustavo Lopes