Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110571
Return-Path: <sebastian@php.net>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 71699 invoked from network); 16 Jun 2020 10:22:15 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 16 Jun 2020 10:22:15 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id 96868180211
	for <internals@lists.php.net>; Tue, 16 Jun 2020 02:07:39 -0700 (PDT)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net
X-Spam-Level: 
X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_40,RCVD_IN_DNSWL_NONE,
	SPF_HELO_NONE,SPF_NEUTRAL autolearn=no autolearn_force=no version=3.4.2
X-Spam-ASN: AS20694 188.94.24.0/21
X-Spam-Virus: No
X-Envelope-From: <sebastian@php.net>
Received: from scarlet.netpirates.net (scarlet.netpirates.net [188.94.27.5])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by php-smtp4.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Tue, 16 Jun 2020 02:07:39 -0700 (PDT)
Received: from p5de2ca78.dip0.t-ipconnect.de ([93.226.202.120] helo=[192.168.178.42])
	by scarlet.netpirates.net with esmtpsa  (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.93)
	(envelope-from <sebastian@php.net>)
	id 1jl7ZC-00020u-9G
	for internals@lists.php.net; Tue, 16 Jun 2020 11:07:38 +0200
To: internals@lists.php.net
References: <CAF+90c9ow-_=DSZ9LFhKzA1ZgHcf0LPt-p7tnhKRcgVUBnLfZw@mail.gmail.com>
Reply-To: internals@lists.php.net
Message-ID: <8e67c7c7-7fca-9959-47bf-256c7884b964@php.net>
Date: Tue, 16 Jun 2020 11:07:36 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101
 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <CAF+90c9ow-_=DSZ9LFhKzA1ZgHcf0LPt-p7tnhKRcgVUBnLfZw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Treat namespaced names as single token, relax
 reserved keyword restrictions
From: sebastian@php.net (Sebastian Bergmann)

Am 16.06.2020 um 10:52 schrieb Nikita Popov:
> https://wiki.php.net/rfc/namespaced_names_as_token

+1

> The RFC comes with a small backwards compatibility break related to names
> that include whitespace, but will hopefully reduce the backwards
> compatibility impact of future reserved keyword additions.

This statement misses the fact that code which uses token_get_all() needs 
to be updated due to the new T_NAME_* tokens. The RFC itself lists this 
change, so that's okay.