Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91767
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain telia.com from 81.236.60.154 cause and error)
To: Fleshgrinder <php@fleshgrinder.com>
References: <CABDNdAHwgx+LJRc_gi9citiypxxWVGFMB+6hrmU+vVYDWCDV_g@mail.gmail.com>
 <56E9CC3E.10205@telia.com> <56E9D45D.4060309@fleshgrinder.com>
 <CAEPJdum+BiXj9Y0o288y1VjopMBnDeDSHmMeHHRQqPXpOMmjsw@mail.gmail.com>
 <56EC611F.7050601@fleshgrinder.com>
Cc: PHP internals <internals@lists.php.net>
Message-ID: <56ED2C1C.3090902@telia.com>
Date: Sat, 19 Mar 2016 11:38:20 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <56EC611F.7050601@fleshgrinder.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC Discussion] Typed Properties
From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=)

Den 2016-03-18 kl. 21:12, skrev Fleshgrinder:
> On 3/17/2016 9:03 AM, Benjamin Eberlei wrote:
>> Sorry to dampen your enthusiasm, but you are going slightly off topic here.
>> Package visibility was tried by Guilherme Blanco before, the way namespaces
>> are implemented this is not possible in PHP in an easy way. As far as i
>> understood him, its way too much work for the little benefit. Typed
>> properties is a huge concept on its own, one small step at a time :-)
>>
> No worries you are not, not at all. I just wanted to thwart you and
> others in directly assigning ...
>
>      final class A {
>          int $x;
>      }
>
> ... to be *public* and obstruct the opportunity of assigning it a
> meaningful new functionality.
>
Well, but if one should assign int $x without visibility keyword a
meaning, shouldn't it be the same as for function y() {} without
keyword, i.e. public?

Of course one can change both, but that sounds like a 8.0 topic.

Regards //Björn