Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50806
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=Zq9YDuFZJn/FpqAeJNqnBpFIutoeoumkqXrMxeXH8jnYMRujV/mzt09+4Zyy/OtW3h
         PwbLSlCUSQ0hGEaAaTd1iEJebjNFqj7kcMfCzHtgbO6ssUV8FKPJLX8fEPlUEDNRC9+p
         /A4skNA+uRy+ZjfedkYhpniCEbd1KDi2gfI+k=
MIME-Version: 1.0
In-Reply-To: <AANLkTikQu9M62XJvJ9mYT_qELN96Zqv7-KiG6sar81u-@mail.gmail.com>
References: <1290879624.7033.826.camel@guybrush> <AANLkTi=174erSkzXxc+bci7P3qB0j2LWZaCnGF2H6_D2@mail.gmail.com>
 <AANLkTinNnhAc3_5BidBxsMG0nY=5pPO+k4BQ_-d5P0xg@mail.gmail.com>
 <AANLkTimYtyunn+Jun-OkTXr=XQK3pxD9yLNOMn5AQJOB@mail.gmail.com> <AANLkTikQu9M62XJvJ9mYT_qELN96Zqv7-KiG6sar81u-@mail.gmail.com>
Date: Thu, 2 Dec 2010 04:03:11 -0600
Message-ID: <AANLkTikECm58xsbTW-7edg6S7SrY4ZHaBL=EFpnWDaWU@mail.gmail.com>
To: =?ISO-8859-1?B?QW5kcukgUvhtY2tl?= <ar@ez.no>
Cc: Patrick ALLAERT <patrickallaert@php.net>, Kalle Sommer Nielsen <kalle@php.net>, 
	=?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>, 
	PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001485f9481ebf2cfd04966a8803
Subject: Re: [PHP-DEV] RFC: Making T_FUNCTION optional in method declarations
From: dukeofgaming@gmail.com (dukeofgaming)

--001485f9481ebf2cfd04966a8803
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

How about deprecation then?

On Thu, Dec 2, 2010 at 3:58 AM, Andr=E9 R=F8mcke <ar@ez.no> wrote:

> On Thu, Dec 2, 2010 at 10:34 AM, Patrick ALLAERT <patrickallaert@php.net
> >wrote:
>
> > 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 "functio=
n"
> > >> (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 ;-)
> >
> > Shouldn't we get rid of that kind of pre-PHP5 stuff _before_
> > introducing the possible omission of T_FUNCTION?
>
>
> Why?
>
> This will break lots of code, does it improve anything while at it? Is
> 'var'
> hindering anything? Is it taking up a lot of code?
> If it is removed then that should be in trunk aka "6.0" the 2nd , and not
> in
> 5.x.
>

--001485f9481ebf2cfd04966a8803--