Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92139
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.51 as permitted sender)
To: internals@lists.php.net
References: <56ED495C.80809@fleshgrinder.com>
 <57069A72.7030100@fleshgrinder.com>
Message-ID: <5706A182.6080401@gmail.com>
Date: Thu, 7 Apr 2016 19:05:54 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <57069A72.7030100@fleshgrinder.com>
Content-Type: multipart/alternative;
 boundary="------------030408000100080208040505"
Subject: Re: [PHP-DEV] Access and Visibility Modifiers
From: rowan.collins@gmail.com (Rowan Collins)

--------------030408000100080208040505
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Fleshgrinder wrote on 07/04/2016 18:35:
> I would like to change above definition for properties since the*var*
> deprecation was voted negative:
>
> # Properties
> private   := limited to the current class
> protected := limited to the current and child classes
> var       := limited to the current assembly
> public    := global

I'm not convinced of the value of reusing the keyword in this way. To 
me, there is nothing in the term "var" that means "slightly less than 
public", and if we want to have package/assembly/whatever visibility, we 
should reserve a new keyword for that use.

Meanwhile, it might be worth checking the list archives for previous 
discussions of package visibility; I know it has come up a couple of 
times recently, in various forms, so it would be good not to repeat the 
same points again and again.

Regards,
-- 
Rowan Collins
[IMSoP]

--------------030408000100080208040505--