Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65045
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50FC11AD.6080506@zerocue.com>
References: <CAF+90c_girfbcPBb8rCV3bPNR2Hsd5gyRPB+VArCfqjPPqG5DQ@mail.gmail.com>
	<CAF+90c9=HgRLHv4o=5dGkQzZPC5Q0tbPC8GD9AZ13Jwkr0pOcw@mail.gmail.com>
	<4ED7146272E04A47B986ED49E771E347BB3D6ABCB3@Ikarus.ameusgmbh.intern>
	<50EC5F8F.8010703@mrclay.org>
	<CAF+90c96OZcBfDEQDEwHVEG78HTirhKONXczEhZUvxQg10MNhA@mail.gmail.com>
	<50EF3C9C.3020701@sugarcrm.com>
	<CAF+90c-EPHHeQdNoE=bXAzwbXG77NSndqux5ptQ__EoacJ3Z2A@mail.gmail.com>
	<50FC11AD.6080506@zerocue.com>
Date: Sun, 20 Jan 2013 17:02:33 +0100
Message-ID: <CAF+90c-AHg+6eLf4=HvzfHw_5JA933P1p63Ww8DQKfP-UB7j6g@mail.gmail.com>
To: Clint Priest <cpriest@zerocue.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d040890c1fba98204d3ba7811
Subject: Re: [PHP-DEV] [RFC] Alternative typehinting syntax for accessors
From: nikita.ppv@gmail.com (Nikita Popov)

--f46d040890c1fba98204d3ba7811
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Jan 20, 2013 at 4:47 PM, Clint Priest <cpriest@zerocue.com> wrote:

>
> On 1/20/2013 9:26 AM, Nikita Popov wrote:
>
>> I now added a patch for this proposal: https://gist.github.com/**4579298<https://gist.github.com/4579298>(For
>> more detailed individual commits see here:
>> https://github.com/nikic/php-**src/commits/alternativeSyntax<https://github.com/nikic/php-src/commits/alternativeSyntax>
>> )
>>
> One thing I hadn't noticed is that the proposal was to move the typehint,
> what happens in this case then:
>
> public DateTime $date {
>     get;
>     set(stdClass $value);
> }
>
> Would the above produce a compilation error on the stdClass part?
>

Yes, that's an error. And I'm not sure what that is supposed to mean in the
first place (it has two different typehints at two different places...)

This proposal will allow a typehint before the property name and only
there. Allowing one in both places doesn't make much sense to me.

Nikita

--f46d040890c1fba98204d3ba7811--