Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64534
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mrclay.org from 50.22.11.19 cause and error)
References: <CAF+90c_girfbcPBb8rCV3bPNR2Hsd5gyRPB+VArCfqjPPqG5DQ@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAF+90c_girfbcPBb8rCV3bPNR2Hsd5gyRPB+VArCfqjPPqG5DQ@mail.gmail.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-ID: <19D80B01-BE88-4119-8A15-B631A96060E5@mrclay.org>
Cc: PHP internals <internals@lists.php.net>
Date: Fri, 4 Jan 2013 18:31:15 -0500
To: Nikita Popov <nikita.ppv@gmail.com>
Subject: Re: [PHP-DEV] [RFC] Alternative typehinting syntax for accessors
From: steve@mrclay.org (Steve Clay)

Would the following two be exactly functionally equivalent?

public Foo $foo;

public $foo {
    get;
    set(Foo $value) { $this->foo =3D $value; }
}

We should also consider how an author would allow type-hinted properties to a=
ccept NULL as a new value, in both proposals.

Steve
--=20
http://www.mrclay.org/

On Jan 4, 2013, at 9:41 AM, Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals!
>=20
> I already brought this up before, but I think the discussion at that time
> was not very constructive and largely off-topic, so I'm bringing it up
> again. To make sure everything is clear I wrote an RFC document:
>=20
> https://wiki.php.net/rfc/propertygetsetsyntax-alternative-typehinting-synt=
ax
>=20
> This RFC proposes an alternative syntax for typehinting accessors, which
> will in particular also allow to typehint properties directly, even if no
> accessors are used (public DateTime $date).
>=20
> What are your opinions on this?
>=20
> Thanks,
> Nikita