Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126225
Precedence: bulk
MIME-Version: 1.0
References: <e14e2b20-1999-4c32-8388-df906c95bae6@gmail.com>
In-Reply-To: <e14e2b20-1999-4c32-8388-df906c95bae6@gmail.com>
Date: Mon, 27 Jan 2025 00:10:13 +0100
Message-ID: <CAPyj-LDTMMnPd_nX=9-Wx4mVzs9j8cj4TYCf253m4wu+m4ePKQ@mail.gmail.com>
Subject: Re: [PHP-DEV] Behaviour of ReflectionClass::getStaticPropertyValue()
 for uninitialized typed properties
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: tovilo.ilija@gmail.com (Ilija Tovilo)

Hi Niels

On Sun, Jan 26, 2025 at 7:43=E2=80=AFPM Niels Dossche <dossche.niels@gmail.=
com> wrote:
>
> I'm looking for feedback on a bugfix for https://github.com/php/php-src/i=
ssues/12856.
> Fix PR: https://github.com/php/php-src/pull/17590
>
> So the alternative idea, the one implemented in my PR, would be this:
>
> - If the property is uninitialized, and $def_value is not provided, then =
throw a ReflectionException with message "Property ... is not initialized a=
nd no default was provided".
> - If the property is uninitialized, and $def_value IS provided, then retu=
rn $def_value.
> - In all other cases, the behaviour stays the same as it was.

I agree that this is the right approach. The proposed behavior is also
in line with native property access, with or without ??.
https://3v4l.org/S3mf8

Ilija