Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105206
MIME-Version: 1.0
References: <CAG9XoMRbcPP6HFOoyY0Qj4vwEtG-q=dGg=tnxyurmkF4p6vsoA@mail.gmail.com>
 <CAF+90c-RkaYkgcbxH2oVG4pkdpAdYO=K4ahmn3A-oPea_TcfKg@mail.gmail.com>
In-Reply-To: <CAF+90c-RkaYkgcbxH2oVG4pkdpAdYO=K4ahmn3A-oPea_TcfKg@mail.gmail.com>
Date: Wed, 10 Apr 2019 15:01:22 +0200
Message-ID: <CAG9XoMTz710myHnT=U=1MZc8j=xYVAdFSgEDN7fY+oNBPkK2Uw@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004fe48505862cab96"
Subject: Re: [PHP-DEV] Unset static properties
From: benjamin.morel@gmail.com (Benjamin Morel)

--0000000000004fe48505862cab96
Content-Type: text/plain; charset="UTF-8"

> We could add support for this, but as the general consensus is that we'd
much rather remove support for unsetting declared object properties (if we
could cover the lazy loading use case in a different way), I don't think it
makes sense to allow this.

Ok, thanks. Just wanted to double check.

Note that I'm actually liking the ability to unset declared properties for
2 reasons:

- lazy loading, as you mentioned
- ability to differentiate between unloaded properties, and properties
loaded as null from the database (useful in data mappers)

Ben

--0000000000004fe48505862cab96--