Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23421
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <4468F219.8030806@album.co.nz>
Date: Tue, 16 May 2006 09:26:49 +1200
Organization: Album Limited
User-Agent: Mail/News 1.5 (X11/20060309)
MIME-Version: 1.0
To: Zeev Suraski <zeev@zend.com>
CC: Jason Garber <jason@ionzoft.com>,  internals@lists.php.net
References: <785810036.20060511193536@ionzoft.com> <7.0.1.0.2.20060515210559.06acd350@zend.com>
In-Reply-To: <7.0.1.0.2.20060515210559.06acd350@zend.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] private, protected, readonly, public
From: jasper@album.co.nz (Jasper Bryant-Greene)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Zeev Suraski wrote:
> I have to say that in second thought (after realizing what you really
> meant) it sounds like a very useful feature.
[snip]
> In order to push complexity down I'd avoid making this yet another
> modifier, and in fact make this an access level, on par with
> private/protected/public, that would behave like public, except for when
> outside the object scope (i.e., have it between protected and public). 
> One of the trickey things would be finding an acceptable name, since
> 'readonly' implies something which this variable isn't (it's very much
> writable, from the right places).  Maybe something like 'visible' (of
> course preferably we need to find something that begins with 'p'...)

How about... 'package' ;)

Jasper
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEaPIZFfAeHhDzT4gRA6MwAJ95DrFGcKmn724VR2y8kaKrpNychwCgm4Ep
U84/fYGcy2JjbwlIBBlBBqI=
=G9a4
-----END PGP SIGNATURE-----