Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23477
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <7.0.1.0.2.20060516144030.039abe98@zend.com>
Date: Tue, 16 May 2006 14:41:31 -0700
To: Marcus Boerger <helly@php.net>
Cc: Zeev Suraski <zeev@zend.com>,PHP internals <internals@lists.php.net>
In-Reply-To: <596643859.20060516233753@marcus-boerger.de>
References: <785810036.20060511193536@ionzoft.com>
	<44647B7A.2070301@php.net>
	<932738738.20060513112734@marcus-boerger.de>
	<837405862.20060513223403@ionzoft.com>
	<36828701.20060514110529@marcus-boerger.de>
	<31269879.20060514221212@marcus-boerger.de>
	<1327845846.20060514222154@marcus-boerger.de>
	<1562034641.20060516203354@marcus-boerger.de>
	<7.0.1.0.2.20060516235201.090f10a8@zend.com>
	<7.0.1.0.2.20060516142654.02c78380@zend.com>
	<596643859.20060516233753@marcus-boerger.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [PHP-DEV] private, protected, readonly, public
From: andi@zend.com (Andi Gutmans)

Where would readable be enforced? Would it try and prevent getting 
references to it? Are there any internal functions/classes which need 
fixing to honor readable?

I think these answers would really be helpful.

Thanks.

Andi

At 02:37 PM 5/16/2006, Marcus Boerger wrote:
>Hello Andi,
>
>   that is why most here already switched to "public readable".
>
>best regards
>marcus
>
>Tuesday, May 16, 2006, 11:31:14 PM, you wrote:
>
> > I can't quite explain it but for me the ability to work-around
> > private with methods which are able to access the private variable,
> > is different than marking a property as read-only but it not being
> > read-only in all semantics. Probably because private variables do
> > often have getters and setters, whereas something which is marked as
> > read-only (like a harddrive) tends to be read-only always.
>
> > Andi
>
> > At 02:08 PM 5/16/2006, Zeev Suraski wrote:
> >>>However, the reason i write this mail is that you said there could be
> >>>problems. Well this is deply integrated  in the handlers and they don't
> >>>let you out. In other words if this stuff is not working then the whole
> >>>PHP 5+ object model is broken. Or in other words, if this is broken alot
> >>>of other stuff regarding object handling is already broken.
> >>
> >>You're probably right about this one.  You can already return a
> >>reference to a private variable today and change it.  Andi - did you
> >>mean something else?
>
>
>
>
>Best regards,
>  Marcus