Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50634 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87069 invoked from network); 27 Nov 2010 18:30:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Nov 2010 18:30:53 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.161.42 mail-fx0-f42.google.com Received: from [209.85.161.42] ([209.85.161.42:54478] helo=mail-fx0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2B/71-14730-B5E41FC4 for ; Sat, 27 Nov 2010 13:30:52 -0500 Received: by fxm11 with SMTP id 11so2338886fxm.29 for ; Sat, 27 Nov 2010 10:30:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=swqHpA7CoZyWVBTON/GandMIyalAHt7942iufvmve2k=; b=R97KF97Al/8niIRSK7uCtNut340IK9YkC3DOCbzI49av79WVHcWuPgomDd5Xc0sJSy kFc0JXButTNCr8y0ysnqJqmegZfnTAnTSLMWYOKJZd71jVSC/MQc1OqdsdX/8Gf7Ss1o kOkUVVeUAknmC1T41BzcHkzjDYmFpt/62+9Ws= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ElfukDCr+8rpYbLS11U6U0Ys3FlyQOnp7QiiQFliy0oRf0JZmKs651t21cFJQqlqQ4 4KOHOzQWQdBe6692X81O0uOQse9W11bHWelFa29ppPUaymwqwlPrYwfuCEGX/jd/1DAl LP9MKl5ytmCYtNpipUAC9ZVkWyRxrG+sShy90= MIME-Version: 1.0 Received: by 10.223.107.66 with SMTP id a2mr3392216fap.92.1290882645930; Sat, 27 Nov 2010 10:30:45 -0800 (PST) Received: by 10.223.83.142 with HTTP; Sat, 27 Nov 2010 10:30:45 -0800 (PST) In-Reply-To: References: <1290879624.7033.826.camel@guybrush> Date: Sat, 27 Nov 2010 19:30:45 +0100 Message-ID: To: Pierrick Charron Cc: =?ISO-8859-1?Q?Johannes_Schl=FCter?= , PHP internals list Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] RFC: Making T_FUNCTION optional in method declarations From: pierre.php@gmail.com (Pierre Joye) +1 if "While technically possible this RFC suggests that the following shall NOT be valid for keeping the code readable " also means that the patch implements it as well (force the function visibility property usage). 2010/11/27 Pierrick Charron : > +1 > > 2010/11/27 Johannes Schl=FCter > >> Hi, >> >> every now and then while writing classes I forget to add the "function" >> keyword between my visibility modifier and the method name in a class >> declaration. I don't think it is required for readability and it is not >> needed by the parser to prevent conflicts, I therefore propose the >> following RFC incl. patch to allow writing >> >> =A0 =A0 =A0 =A0class Foo { >> =A0 =A0 =A0 =A0 =A0 =A0public bar() { >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0echo "Hello World"; >> =A0 =A0 =A0 =A0 =A0 =A0} >> =A0 =A0 =A0 =A0} >> >> Without T_FUNCTION token. In my opinion an access modifier /public, >> private protected, static, final) should still be required for keeping >> readability. >> >> RFC: http://wiki.php.net/rfc/optional-t-function >> Patch: http://schlueters.de/~johannes/php/zend_optional_t_function.diff >> >> johannes >> >> >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> > --=20 Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org