Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64483
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50E4712E.3060804@mrclay.org>
References: <50E41BB6.4030901@zerocue.com>
	<50E4712E.3060804@mrclay.org>
Date: Wed, 2 Jan 2013 11:34:42 -0700
Message-ID: <CAFMT4NqY-wPNZJhLwd8Yrfmsr-DmYko=uBiEvKBBi-Pzu9JnFA@mail.gmail.com>
To: Steve Clay <steve@mrclay.org>
Cc: Clint Priest <cpriest@zerocue.com>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] [PHP-RFC] Property Accessors 1.2 for Final Review
 before Vote
From: morrison.levi@gmail.com (Levi Morrison)

On Wed, Jan 2, 2013 at 10:41 AM, Steve Clay <steve@mrclay.org> wrote:
> On 1/2/13 6: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
>
>
> The RFC does not specify whether it's a fatal error to define a class
> (directly or via extends/traits) which has both a traditional property and
> accessor with the same name, but I think this should be prohibited to avoid
> confusion.

I think it is explained in the RFC:
https://wiki.php.net/rfc/propertygetsetsyntax-v1.2#shadowing but the
code example doesn't reflect that. Perhaps my understanding is flawed.