Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63383
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zerocue.com designates 74.115.204.51 as permitted sender)
To: Nikita Popov <nikita.ppv@gmail.com>
CC: "internals@lists.php.net" <internals@lists.php.net>
Thread-Topic: [PHP-DEV] [PHP-DEV [RFC] Property Accessors v1.2
Thread-Index: Ac2oOZ3+vAOzWRcnRpOb6a/hOVK5+AATwXAAAB0xg5A=
Date: Sat, 13 Oct 2012 04:47:55 +0000
Message-ID: <9570D903A3BECE4092E924C2985CE485612B5753@MBX202.domain.local>
References: <9570D903A3BECE4092E924C2985CE485612B53E4@MBX202.domain.local>
 <CAF+90c9Sb786Cg=jBS=HUMkWaX60XGKNhVPUqrcoU7pQaub_=A@mail.gmail.com>
In-Reply-To: <CAF+90c9Sb786Cg=jBS=HUMkWaX60XGKNhVPUqrcoU7pQaub_=A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: RE: [PHP-DEV] [PHP-DEV [RFC] Property Accessors v1.2
From: cpriest@zerocue.com (Clint Priest)

The problem with that Nikita is that it would need a variable storage locat=
ion, which would mean a hidden, auto-implemented property.  You were dead-s=
et against that from the get go.  Keep in mind that property accessors are =
not properties, real properties will take over the accessor, this could onl=
y be done from within the setter of an accessor, but there isn't any way to=
 create an accessor named $Hours which accesses a variable named $Hours.

In any case, your example below could be implemented without automatic crea=
tion simply by doing the backing yourself, such as:

private $myFoo;

public $foo {
	get() { return $this->myFoo; }
	protected set($x) { $this->myFoo =3D $x; }
}

Again, without another "variable store" automatic properties goes out the d=
oor, can't really have one without the other.

Shall I hold off on this discussion point before proceeding?

> -----Original Message-----
> From: Nikita Popov [mailto:nikita.ppv@gmail.com]
> Sent: Friday, October 12, 2012 5:48 AM
> To: Clint Priest
> Cc: internals@lists.php.net
> Subject: Re: [PHP-DEV] [PHP-DEV [RFC] Property Accessors v1.2
>=20
> 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 da=
ys:
> >
> > https://wiki.php.net/rfc/propertygetsetsyntax-as-implemented
> >
> > If you could read it over, make sure I have all of your concerns correc=
tly addressed and we can leave this open for the two week
> waiting period while I make the final code changes.
> >
> > -Clint
>=20
> I've been thinking a bit about the automatic properties again, and notice=
d that I forgot to name one use case: Asymmetric accessor
> visibility. Automatic properties may be useful in that context, so that y=
ou can write "public $foo { get; protected set; }" (though they
> don't necessarily need to be implemented as properties with auto generate=
d code, rather just properties with more detailed visibility
> handling [a bit related to the stuff Amaury has been saying]).
>=20
> Nikita