Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:31068
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain sci.fi from 63.208.196.171 cause and error)
Message-ID: <469E7BBB.2090303@sci.fi>
Date: Wed, 18 Jul 2007 23:44:43 +0300
Reply-To:  jani.taskinen@iki.fi
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Sara Golemon <pollita@php.net>
CC: Arnold Daniels <info@adaniels.nl>,  internals@lists.php.net
References: <469E765C.2080101@adaniels.nl> <469E7AFC.4060607@php.net>
In-Reply-To: <469E7AFC.4060607@php.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: private_write/protected_write properties
From: jani.taskinen@sci.fi (Jani Taskinen)

So the short answer is: no. End of story.

Don't start another endless thread about something that "would be nice" when we 
have bigger issues on the table that need to be solved before any release, be it 
  alpha/beta/whatever, can be done..

--Jani


Sara Golemon kirjoitti:
>> I'll probably be lynched for bringing up this subject again, since it 
>> caused a long discussion a year ago. Anyway I look in the archives and 
>> there was never a real conclusion made, so I'm bringing it up again. 
>> This time for a feature I personally would like to see in PHP 6.
>>
>> Very often I want to be able to be get a property publicly, while only 
>> being able to set it within the class. You can solve this by using a 
>> getPropery() method or by using __get($property), but this feels more 
>> like a workaround. I think the private/public state of properties is 
>> becoming more important now that using public frameworks is becoming 
>> main stream. Therefor I believe this would be a good addition.
>>
> Unfortunately, there are a few caveats to this when used with objects, 
> resources, and arrays.  The simplest way to explain would be to show 
> some sample code:
> 
> class foo {
>   public $bar = 'baz';
> }
> 
> class myclass {
>   protected_write $f;
>   private_write $fp;
> 
>   function __construct() {
>     $this->f = new foo;
> 
>     $this->fp = fopen('somefile.txt', 'r');
>   }
> }
> 
> $m = new myclass;
> 
> $F = $myclass->f;
> $F->bar = 'blong';
> 
> $FP = $myclass->fp;
> fclose($FP);
> 
> 
> The explanation of arrays is a bit more involved, but it's got some 
> gotchas too...
>