Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105204
MIME-Version: 1.0
Date: Wed, 10 Apr 2019 14:20:16 +0200
Message-ID: <CAG9XoMRbcPP6HFOoyY0Qj4vwEtG-q=dGg=tnxyurmkF4p6vsoA@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000494d8a05862c18ae"
Subject: Unset static properties
From: benjamin.morel@gmail.com (Benjamin Morel)

--000000000000494d8a05862c18ae
Content-Type: text/plain; charset="UTF-8"

Hi internals,

I came across this when playing with static properties:

    class A {
        public static int $x;
    }

    // This throws, as expected:
    // Error: Typed static property A::$x must not be accessed before
initialization
    echo A::$x;

    // Once we initialize the property:
    A::$x = 1;
    echo A::$x; // 1

    // There is no way to revert the property back to uninitialized state:
    // Error: Attempt to unset static property A::$x
    unset(A::$x);

Is this expected behaviour? I don't currently have a use case for this, but
am wondering whether it is consistent to disallow un-initializing a static
property when it's allowed to be uninitialized in the first place.

Cheers,
Ben

--000000000000494d8a05862c18ae--