Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61311
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.170 as permitted sender)
MIME-Version: 1.0
Sender: amaury.bouchard@gmail.com
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 17:24:52 +0200
Message-ID: <CAPaKmR=rveMOaGXWjx=9s2-fU86BRe90yScwbd60hJN+-g6c3w@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=e89a8f83a73537fcf004c4f40984
Subject: Re: [PHP-DEV] RFC Proposal - Attributes read/write visibility
From: amaury@amaury.net (Amaury Bouchard)

--e89a8f83a73537fcf004c4f40984
Content-Type: text/plain; charset=ISO-8859-1

2012/7/16 Nikita Popov <nikita.ppv@gmail.com>

> 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?
>
>
Yes, but only if you have to write an accessor.
If you just want an attribute that is:
- readable from everywhere
- writable from the current class only

With my syntax:
    public:private $a;  (read it aloud "public reading, private writing")

With the existing RFC:
    public $a {
        private set { $this->a = $value; }
    }

Which one is better? Why should I write code for that?

If you read the existing RFC, you'll see that all examples involve a
specific case: when you have a "fake" attribute, which manipulates date
stored in other attributes. The given example is an $Hours attributes,
which is calculated from the private $Seconds attribute.
Again, it could be very useful. But it doesn't work all the time.

--e89a8f83a73537fcf004c4f40984--