Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121758
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
In-Reply-To: <054a1e3e-f860-4596-83a9-9f557c6fd316@gmail.com>
Date: Wed, 22 Nov 2023 16:27:19 +0100
Cc: PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <3B56EC97-9D45-4302-B555-367F43C288EC@gmail.com>
References: <2b4591c1-f999-49b5-8061-67db816aa0da@gmail.com>
 <054a1e3e-f860-4596-83a9-9f557c6fd316@gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Subject: Re: [PHP-DEV] [RFC][Discussion] Harmonise "untyped" and "typed"
 properties
From: claude.pache@gmail.com (Claude Pache)



> Le 21 nov. 2023 =C3=A0 00:08, Rowan Tommins <rowan.collins@gmail.com> =
a =C3=A9crit :
>=20
> I've revised the RFC; it now proposes to keep the implicit "=3D null" =
for untyped properties, although I'm still interested in suggestions for =
other strategies around that.=20

Hi,

If you really want untyped property not being implicitly initialised to =
=E2=80=9Cnull=E2=80=9D in the long term, here is my suggestion:

1. In 8.next, deprecate untyped property without initialiser, suggesting =
to add an explicit =E2=80=9C=3D null=E2=80=9D (one deprecation notice =
per class definition containing at least one untyped property without =
initialiser);
2. In 9.0, an untyped property without initialiser becomes a syntax =
error;
3. Later, reintroduce untyped property without initialiser with the new =
semantics.

=E2=80=94Claude