Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63562
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+90c8T3yVja_kL=zrh=QSZW9jyQw1Kq9LLMi+sNqdH4sOrgQ@mail.gmail.com>
References: <9570D903A3BECE4092E924C2985CE485612C2595@MBX214.domain.local>
 <CAPaKmRmghPKO-4wTFXVTpiUeb8mY34B799PgTLmiTtx3fw-ZkQ@mail.gmail.com> <CAF+90c8T3yVja_kL=zrh=QSZW9jyQw1Kq9LLMi+sNqdH4sOrgQ@mail.gmail.com>
Date: Sat, 20 Oct 2012 12:37:12 +0200
Message-ID: <CAPaKmRk1LYxKV=SQBj87E0S_4j68oPgm+_8KLj_NUDnsJZNQig@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: Clint Priest <cpriest@zerocue.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf303a360b38489a04cc7b35ca
Subject: Re: [PHP-DEV] [RFC] Accessors : read-only / write-only keywords
From: amaury@amaury.net (Amaury Bouchard)

--20cf303a360b38489a04cc7b35ca
Content-Type: text/plain; charset=ISO-8859-1

2012/10/20 Nikita Popov <nikita.ppv@gmail.com>

> Could you maybe explain where exactly "const" would be used?
>

Well "const" and "read-only" have the exact same meaning. You can replace
one by the other. So why create a new keyword?



> Please
> don't forget that we do not use your "foo:bar" syntax, so where would
> the "const" go with the currently used syntax?
>

Don't be rude. It's not a "foo:bar" syntax sent no matter how on this
mailing-list. It was an argumented RFC proposal, with an associated patch
(but yeah, who cares?).
If you want to give it a silly nickname, I'd prefer "public:private".  :-)


The RFC was:
    public read-only $a {
        get { return $this->_a; }
    }

It could be:
    public const $a {
        get { return $this->_a; }
    }

Is it so different that it needs a new keyword?

--20cf303a360b38489a04cc7b35ca--