Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93545
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain thomasbley.de from 85.13.128.151 cause and error)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: ALL-INKL Webmail 2.11
To: ajf@ajf.me, internals@lists.php.net, smalyshev@gmail.com
Cc: ocramius@gmail.com, bensor987@neuf.fr, me@kelunik.com
Message-ID: <20160525221727.9A5A11A80649@dd1730.kasserver.com>
Date: Thu, 26 May 2016 00:17:27 +0200 (CEST)
Subject: Re: [PHP-DEV] [RFC][Vote] Typed Properties
From: mails@thomasbley.de ("Thomas Bley")

Currently the rfc also checks the properties for being initialized.
I think it's still faster than most userland implementations using __get() for type checks and parsing phpdoc for type information.

Regards
Thomas

Stanislav Malyshev wrote on 25.05.2016 23:56:

> Hi!
> 
>> var_dump($a->w); // Fatal error, uninitialized...
> 
> This means every read access to a property should be checked for it
> being typed, and every access to a typed property should be checked for
> it being initialized. I'm concerned there might be a performance hit for
> this.
> 
> Also, this means no access for a property - even defined one - is safe,
> and if you want to avoid fatal errors, you need to check every access,
> at least if you suspect typed properties may be involved. And, of
> course, there's no function in the RFC to actually check it.
> -- 
> Stas Malyshev
> smalyshev@gmail.com
> 
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>