Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50719
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.170 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        b=V6wObA1qpsUpMvlm+7icvI5hBMRweHjmYc7B6A3bA0ybYbAjGPJEZdwUEbPDWitvAz
         Pau6wJNTpzg5g0OzwAGBcN3WPDgskLm9FWrpbmifxxXQnEKd/DRtaDCuzJEkEm00YRLR
         AZAWhQ9ueeqEPM9qqw7JdnsGSYsjbtIfwntK4=
MIME-Version: 1.0
Sender: patrick.allaert@gmail.com
In-Reply-To: <1290879624.7033.826.camel@guybrush>
References: <1290879624.7033.826.camel@guybrush>
Date: Tue, 30 Nov 2010 11:00:06 +0100
Message-ID: <AANLkTi=174erSkzXxc+bci7P3qB0j2LWZaCnGF2H6_D2@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC: Making T_FUNCTION optional in method declarations
From: patrickallaert@php.net (Patrick ALLAERT)

2010/11/27 Johannes Schl=C3=BCter <johannes@schlueters.de>:
> 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
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0class Foo {
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0public bar() {
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0echo "Hello World"=
;
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0}
> =C2=A0 =C2=A0 =C2=A0 =C2=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

With this patch, something looks inconsistent to me:
Both properties and methods have a visibility
(public|protected|private) and a keyword: "var" (T_VAR) and "function"
(T_FUNCTION) respectively.
However "private var $foo;" generates a fatal error but "private
function foo(){}" not?

Cheers,
--=20
Patrick Allaert
---
http://code.google.com/p/peclapm/ - Alternative PHP Monitor