Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93568
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <e194be7d-2d72-945c-b8de-245e91f6f239@thefsb.org>
References: <20160525215208.034FC1A801B3@dd1730.kasserver.com>
	<e194be7d-2d72-945c-b8de-245e91f6f239@thefsb.org>
Date: Thu, 26 May 2016 10:02:46 -0500
Message-ID: <CAO3MkaD==1jQvS_cRbDrBQ7nkoBvoAaavmgxeMiP0mSKXL7eRQ@mail.gmail.com>
To: Tom Worster <fsb@thefsb.org>, Thomas Bley <mails@thomasbley.de>, ajf@ajf.me, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113ce0d23e9e890533c015dd
Subject: Re: [PHP-DEV] [RFC][Vote] Typed Properties
From: neclimdul@gmail.com (James Gilliland)

--001a113ce0d23e9e890533c015dd
Content-Type: text/plain; charset=UTF-8

>
> If you want, you can easily write a backwards-compatible new class that
> uses declared type properties with
> public int $property = null;

And for those pesky third party libraries that forgot to set = NULL on
their property definition there's a backwards compatible accessor too.

$foo = $obj->bar ?? NULL;

Sarcasm aside, I still can't figure out how fundamentally changing how
people interact with uninitialized properties like this improves developer
experience. Can someone explain a case where this is better and catches a
bug or something? Since this is a new feature I would assume its not
covered by "BC" but this seems like a painful gotcha for people developing
across typed and untyped code.

--001a113ce0d23e9e890533c015dd--