Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91738
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <56EAAF13.20001@php.net>
References: <CABDNdAHwgx+LJRc_gi9citiypxxWVGFMB+6hrmU+vVYDWCDV_g@mail.gmail.com>
	<56EAAF13.20001@php.net>
Date: Thu, 17 Mar 2016 10:27:21 -0400
Message-ID: <CABDNdAEHvD2EMR4JKGoPd8v3NPmY2L2d9eAc20_oi93qwvMnFg@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC Discussion] Typed Properties
From: pjsturgeon@gmail.com (Phil Sturgeon)

Quick update folks, the RFC patch now respects strict mode, so will be
weak by default and strict if enabled.

I'll update the RFC to reflect this soon, but I'm busy today and it
won't get done until tomorrow.

Also there is definitely no void keyword for properties.

We'll move onto working out default values and references shortly.
There are some great points in here, so let me get 0.3.0 of the RFC
out and we'll get onto that.

On Thu, Mar 17, 2016 at 9:20 AM, Fran=C3=A7ois Laupretre <francois@php.net>=
 wrote:
> Hi,
>
> Le 16/03/2016 17:36, Phil Sturgeon a =C3=A9crit :
>>
>> Hello everyone,
>>
>> I have completed the draft for an RFC, to add Typed Properties. The
>> patch has been written by the one and only Joe Watkins.
>>
>> https://wiki.php.net/rfc/typed-properties
>>
>
> Maybe you can add a reference to a discussion we had some months ago :
> http://www.serverphorums.com/read.php?7,1296955. This was not exactly abo=
ut
> typed properties but it also concludes that enforcing type checks on ever=
y
> write access requires typed zvals, which would be extremely powerful, but
> also a very complex task (mostly for performance reasons).
>
> Regards
>
> Fran=C3=A7ois