Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61293
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 74.125.82.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAF+90c-yQe4Hjh=1KUAhN0XFkSp1OXevcvuHXiBJ2Y0isU=QeQ@mail.gmail.com>
References: <CAPaKmRmn+L081722PHdzJFEO4wRyGTixacLZ38FTyBr-s8Up3w@mail.gmail.com>
 <CAF+90c-yQe4Hjh=1KUAhN0XFkSp1OXevcvuHXiBJ2Y0isU=QeQ@mail.gmail.com>
Date: Mon, 16 Jul 2012 14:20:05 +0100
Message-ID: <CAN+gjSeyZfEWHsV_BbJSSoZhutZ2j0O0JBS_NpfSrS7+C+JGYg@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: Amaury Bouchard <amaury@amaury.net>, internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] RFC Proposal - Attributes read/write visibility
From: ajfweb@googlemail.com (Andrew Faulds)

An ugly, confusion-causing syntax.

On 16 July 2012 14:11, Nikita Popov <nikita.ppv@gmail.com> wrote:
> On Sun, Jul 15, 2012 at 5:46 PM, Amaury Bouchard <amaury@amaury.net> wrote:
>> Hi,
>>
>> Here is an RFC proposal about a syntax extension for PHP. The purpose is to
>> manage precisely the visbiliy of attributes, by separating reading and
>> writing access.
>>
>> First of all, I know there is already an RFC about attributes ("Property
>> get/set syntax" [1]). Its goal is mainly different, but I'll discuss it
>> lower.
>
> I'm not sure I really understand what this adds over the existing
> getter/setter proposal. read-only and write-only should cover the most
> common cases. If you do need visibility control, it is possible too:
>
> public $property {
>     get { ... }
>     protected set { ... }
> }
>
> So what does this proposal add to it?
>
> Nikita
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>



-- 
Andrew Faulds (AJF)
http://ajf.me/