Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91662
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain telia.com from 81.236.60.156 cause and error)
To: Colin O'Dell <colinodell@gmail.com>,
 Patrick ALLAERT <patrickallaert@php.net>
References: <CAJaRsPu+1-4smkTLACKFavHKqED0gBrz-w42wAVXvj-mYKHZNA@mail.gmail.com>
 <CACwt+JfGyu=Qp-UnLHBjBX4Yc=0T8ii=UD2wCqJQxt5QNffDzg@mail.gmail.com>
 <CAJaRsPv4wRVJBrRotXpwvd4etB0=j2Nh=vODCOgaM9waE5C=aQ@mail.gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Message-ID: <56E71CD3.8030402@telia.com>
Date: Mon, 14 Mar 2016 21:19:31 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAJaRsPv4wRVJBrRotXpwvd4etB0=j2Nh=vODCOgaM9waE5C=aQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC Discussion] "var" Deprecation
From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=)

Den 2016-03-14 kl. 19:14, skrev Colin O'Dell:
>> Forcing people to specify a visibility for properties and not for methods
>> would add yet another inconsistency in the language.
>>
> That's a really good point.  However, I think we currently have a different
> inconsistency: declaring functions without explicit visibility is possible
> without needing an extra (and redundant) keyword.
>
> The inconsistency you mention could easily be solved by a future RFC.  We
> could:
>
>    1. Require visibility for class methods.
>    2. Allow declaring properties without using any keywords.
>    3. Use some other approach?
>
> I don't think we necessarily need to choose an option at this time (or
> perhaps ever).
>
Interesting :)  Think option 1 implies a BC break. Would it also affects 
interface
declarations making public keyword mandatory? Personally I like option 
2, but
feels a bit beyond the scope of this RFC.

Regards //Björn