Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63371
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <9570D903A3BECE4092E924C2985CE485612B53E4@MBX202.domain.local>
References: <9570D903A3BECE4092E924C2985CE485612B53E4@MBX202.domain.local>
Date: Fri, 12 Oct 2012 12:48:28 +0200
Message-ID: <CAF+90c9Sb786Cg=jBS=HUMkWaX60XGKNhVPUqrcoU7pQaub_=A@mail.gmail.com>
To: Clint Priest <cpriest@zerocue.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] [PHP-DEV [RFC] Property Accessors v1.2
From: nikita.ppv@gmail.com (Nikita Popov)

On Fri, Oct 12, 2012 at 7:23 AM, Clint Priest <cpriest@zerocue.com> wrote:
> Alright, here is the updated RFC as per discussions for the last few days:
>
> https://wiki.php.net/rfc/propertygetsetsyntax-as-implemented
>
> If you could read it over, make sure I have all of your concerns correctly addressed and we can leave this open for the two week waiting period while I make the final code changes.
>
> -Clint

I've been thinking a bit about the automatic properties again, and
noticed that I forgot to name one use case: Asymmetric accessor
visibility. Automatic properties may be useful in that context, so
that you can write "public $foo { get; protected set; }" (though they
don't necessarily need to be implemented as properties with auto
generated code, rather just properties with more detailed visibility
handling [a bit related to the stuff Amaury has been saying]).

Nikita