Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124559
Message-ID: <49c17116-8f96-4429-ae56-0024a7981852@gmx.de>
Date: Tue, 23 Jul 2024 16:41:27 +0200
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [RFC] [VOTE] Deprecations for PHP 8.4
Content-Language: de-DE
To: Larry Garfield <larry@garfieldtech.com>,
 php internals <internals@lists.php.net>
References: <USzt7tZZlO1DmAbSTLhD-bqa23FqZn0zk2aah8Ndxgk9c7RY5PefQ8MjbYPUYAzr2_m4Cf-5AI4PuNBTS84rim_FNS6RaT-cWSv714HEvvU=@gpb.moe>
 <CAJp_myW1cGAZT-183cKTEQus1G3KJiW2vHx6GtdYP78pZc1evQ@mail.gmail.com>
 <ffd507a4-7f8d-4e3d-a477-e59c96b582ba@app.fastmail.com>
In-Reply-To: <ffd507a4-7f8d-4e3d-a477-e59c96b582ba@app.fastmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
UI-OutboundReport: notjunk:1;M01:P0:VLIwjukjfZM=;mLVvlCjJ79wBxbjvjIbDDeccHFm
 2P/V0vWbMoZvAA/dKgsdZzOCV5zgRm1K++rcLuodG/eH2TlAybThnWtBwigCWPL7oKcVQdC98
 2mkBFJjGoBiYlkW0MnIoclc4e9E+dANQgPVzBI1kUMNNy5yJarls08CdaX2Szp5g5VDBnrJER
 zkAe6heomfd4mgipgwVVhfL3PCn/N95iZ9E3u+nI2XrgusT5sclqXwsi/2EUf3Twybpur6Yno
 tT/CqujwDCzz3COK2B8UW4oFtYar8EjDv/8zSWQ/Pp/A44Z4EuPqjoJGWB+tgdmkZMc2QQsq/
 QYnpjCDj4OBDiwCkEgivgKH3z4EKjy6iM/uXebiv2FVhoo/XLez/VrvRtqKXzxErx3zGlqsL/
 MVf/7wAD6Abz0Nycb5Ku80IcJoOb6/tx1fop9YntiALzUGGFwnk6GTbBqc1qFGnq45ALxFoFo
 TnvUoyktUi/kxL30dxj98FAouoasWCdTPKBpKRF8MPcEwulP22jCQYjCqQfcEVRHyEpPRsLq2
 V+/ie0hDUrCrGZ0XmURtIjHYdlHtsSwlYzgq4qETP1bQ3DjQNva4LVhBO/9Nao9CRc4eDxWiG
 8OrcgZz8I8cjtUPr4LfuCfin1l5SA4qFMm4/VlMlyBZ1C//geukNgkvjdNm+79PO/B7lZyKRR
 aqfK0NlFkOrM/LY8hzx8saj64arGoDbT2bx1q6mcZ446zwDC/VZsfXjw7CqObijrbCCzgSCsG
 imQ0JLZwSImL7eDQcxK7bJHFTyeQJsf4q+zMtEg7BF633qat6tN9y8HL4NqiMf1XdFlOQIT/a
 8FmLw1yNtozvZT6rKe4UiBOQ==
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 23.07.2024 at 16:04, Larry Garfield wrote:

> On Tue, Jul 23, 2024, at 1:42 PM, Matthew Weier O'Phinney wrote:
>
>> On Fri, Jul 19, 2024 at 12:41=E2=80=AFPM Gina P. Banyard <internals@gpb=
.moe> wrote:
>>
>>> I have opened the vote for the mega deprecation RFC:
>>> https://wiki.php.net/rfc/deprecations_php_8_4
>>
>> The section "Deprecate using a single underscore ''_'' as a class name"
>> indicates that probably the primary reason to deprecate it is a
>> potential future conflict in the pattern matching RFC, where it can be
>> used as a wildcard.
>>
>> However, I see no mention of this character as a wildcard anywhere in t=
hat RFC.
>>
>> Can somebody clarify?
>
> The pattern matching RFC previously listed _ as a wildcard character.
>
> In the discussion a month ago, someone pointed out that `mixed` already =
serves that exact purpose, so having an extra wildcard was removed.
>
> However, a few people indicated a desire to have an explicit wildcard _ =
anyway, even if it's redundant, as it's a more common and standard approac=
h in other languages.  We've indicated that we are open to making that an =
optional secondary vote in the pattern matching RFC if there's enough inte=
rest (it would be trivial), though I haven't bothered to add it to the RFC=
 text yet.
>
> Having _ available could also be used in other "wildcard" or "ignore thi=
s" cases, like exploding into a list assignment or similar, though I don't=
 believe that has been fully explored.
>
> That's the context/background here.  Whether that encourages you to vote=
 for or against that section I leave as an exercise for the reader.

Well, I wonder how that is supposed to work.  Assuming the underscore
would be used as wildcard in a class name context, that could only be
done after using that character as class name is no longer allowed.  So
that would have to wait for the next major PHP version (at least).

Note that I'm not worried about no longer being able to use an
underscore as class name, but rather that this introduces another
inconsistency to our indentifiers.  Disallowing an underscore as
function name is obviously off the table, thanks to gettext.

Christoph