Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64514
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zerocue.com designates 67.200.53.250 as permitted sender)
Message-ID: <50E65726.2070503@zerocue.com>
Date: Thu, 03 Jan 2013 22:14:30 -0600
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: PHP Developers Mailing List <internals@lists.php.net>
References: <50E41BB6.4030901@zerocue.com>
In-Reply-To: <50E41BB6.4030901@zerocue.com>
Content-Type: multipart/alternative;
 boundary="------------050008050504080808080706"
Subject: Re: [PHP-DEV] [PHP-RFC] Property Accessors 1.2 Updates / Clarifications
From: cpriest@zerocue.com (Clint Priest)

--------------050008050504080808080706
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Please note that I have updated and clarified v1.2 with some recent 
feedback:

1) Steve Clay suggested the term Guarded Property and dropping 
Shadowing.  The "Shadowing" section has been renamed to "Guarding," some 
of the wording was updated and the "For Additional Clarity" was updated 
with nearly identical wording Steve suggested which I think brings even 
greater clarity.

2) The parent::$foo issue I recently posted about was changed near the 
end of the "Overloading Properties" section, which shows the proposed 
parent->$Milliseconds form.  Seeing it color coded in this light makes 
it even more appealing and apparent I feel.

3) Removal of Accessor section was added.  This was brought up as a 
question as to what happens and I felt what should be done is what is 
defined there.

Other possible alternatives to number 3:

3a) The public $Foo = 5 declaration would not "shed" it's inherited 
accessors, they would remain or could be re-defined (but not removed).

3b) The public $Foo = 5 declaration would not be allowed with the = 5 
and it would not shed its inherited accessors as 3a

For maximum flexibility, I favor the proposed solution as it provides 
for the most flexibility, it would allow sub-classes to re-define a 
guarded property as a traditional property, or keep it as a guarded 
property (modifying the getter, adding a setter, etc).

On 1/2/2013 5:36 AM, Clint Priest wrote:
> Here is the updated RFC incorporating the feedback from previous 
> rounds of discussion.
>
> https://wiki.php.net/rfc/propertygetsetsyntax-v1.2
>
> I'm posting it for final review so I can move to voting on Jan 7th.
>
> Please note that the current fork is not quite up-to-date with the RFC 
> but will be within a few more days.
>
> -Clint
>

-- 
-Clint

--------------050008050504080808080706--