Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50752
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        b=iV31H2v1sY1aGDyFz4I9ugqJQSlc9P+s1+1hBEurpcsZ9h+j1piyQfrsO14cg6QPmf
         7NfK3sX7xksPIdo5PAHmupYPG4B2sMgN7hMlX1wcT8O1blokXJJmwWYnOWSAg+iztXjc
         2s1UeiRZdujASX2CFreSuuuxz6GSusO0Xblt8=
MIME-Version: 1.0
In-Reply-To: <AANLkTinNnhAc3_5BidBxsMG0nY=5pPO+k4BQ_-d5P0xg@mail.gmail.com>
References: <1290879624.7033.826.camel@guybrush> <AANLkTi=174erSkzXxc+bci7P3qB0j2LWZaCnGF2H6_D2@mail.gmail.com>
 <AANLkTinNnhAc3_5BidBxsMG0nY=5pPO+k4BQ_-d5P0xg@mail.gmail.com>
Date: Tue, 30 Nov 2010 19:00:38 -0600
Message-ID: <AANLkTin1z6Jxu_NocBDjwZ+47hsAMaoJzttU7qquSZHB@mail.gmail.com>
To: Kalle Sommer Nielsen <kalle@php.net>
Cc: Patrick ALLAERT <patrickallaert@php.net>, =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>, 
	PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=0016367b5e429e870a04964ed62d
Subject: Re: [PHP-DEV] RFC: Making T_FUNCTION optional in method declarations
From: dukeofgaming@gmail.com (dukeofgaming)

--0016367b5e429e870a04964ed62d
Content-Type: text/plain; charset=ISO-8859-1

Hi, first time on the lists, guess I'm from userlando too,

+1 for readability, all I ever really look at are "( ... ){" at the end of
the line so I personally don't think it affects readability. Also, this is
the way its done in other languages and I have always found the function
keyword unnecessary in PHP.

Regards,

David

2010/11/30 Kalle Sommer Nielsen <kalle@php.net>

> Hi
>
> 2010/11/30 Patrick ALLAERT <patrickallaert@php.net>:
> > 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?
>
> The "var" keyword is an alias of the "public" keyword for BC with
> PHP4. So it would be illogically to declare a property both private
> and public at the same time ;-)
>
>
>
> --
> regards,
>
> Kalle Sommer Nielsen
> kalle@php.net
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--0016367b5e429e870a04964ed62d--