Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23337
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <44668EF8.1080906@akbkhome.com>
Date: Sun, 14 May 2006 09:59:20 +0800
User-Agent: Mozilla Thunderbird 0.8 (X11/20040926)
MIME-Version: 1.0
To: Hartmut Holzgraefe <hartmut@php.net>
CC: Bastian Grupe <bgrupe@gmail.com>, Jason Garber <jason@ionzoft.com>, 
	internals@lists.php.net
References: <785810036.20060511193536@ionzoft.com> <4464AC64.5050706@gmail.com> <4464C6C9.40307@php.net>
In-Reply-To: <4464C6C9.40307@php.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] private, protected, readonly, public
From: alan@akbkhome.com (Alan Knowles)

Definatly would love to see readonly, It would remove 1000's of lines of 
useless code from 100's of projects - which might make a few more public 
PHP projects readable ;)
It replaces pointless giberish with something explicit clean and elegant..

Looks alot tidier than getters, or __get kludges.

Regards
Alan
Hartmut Holzgraefe wrote:

> Bastian Grupe wrote:
>
>> Uhh... how about using private and only using a "regular"
>> getter (the Java-style) and no setter?
>>
>>    class xx
>>    {
>>       private $bar;
>>
>>       public getBar() { return $bar; }
>>    }
>
>
> i think you're missing the point, the idea is to *not*
> have to write that extra getter line ... less typing
> *and* less error prone ... and easier to read, too IMHO
>
> You didn't want to return $bar in your example, you wanted
> to return $this->bar so you already ran into one of the
> issues here ;)
>