Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61312
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAN+gjSeyZfEWHsV_BbJSSoZhutZ2j0O0JBS_NpfSrS7+C+JGYg@mail.gmail.com>
References: <CAPaKmRmn+L081722PHdzJFEO4wRyGTixacLZ38FTyBr-s8Up3w@mail.gmail.com>
 <CAF+90c-yQe4Hjh=1KUAhN0XFkSp1OXevcvuHXiBJ2Y0isU=QeQ@mail.gmail.com> <CAN+gjSeyZfEWHsV_BbJSSoZhutZ2j0O0JBS_NpfSrS7+C+JGYg@mail.gmail.com>
Date: Mon, 16 Jul 2012 16:25:35 +0100
Message-ID: <CA+yzxZj_8Bb0GKdxUmzcwiSqcpiiGJwWfLQDt1GtxzgFt0jGmw@mail.gmail.com>
To: Andrew Faulds <ajfweb@googlemail.com>
Cc: Nikita Popov <nikita.ppv@gmail.com>, Amaury Bouchard <amaury@amaury.net>, internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] RFC Proposal - Attributes read/write visibility
From: admacedo@gmail.com (Daniel Macedo)

You already have the read-only/write-only option proposed on that RFC
- by not defining set and vice-versa for write only - or by inserting
new keywords (not sure if this is needed/optimal).

And nowhere in PHP do we have the syntax you propose as A:B, and I
even recall a short array [a:1, b:2] syntax from being promptly
rejected in the past, although I can't recall the argument against it.

Plus that RFC can allow for additional implementation of something
like a lambda/other function calls; a lot of things way more
useful/interesting to see than just controlling visibility.