Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109669 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 65223 invoked from network); 15 Apr 2020 21:57:24 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 15 Apr 2020 21:57:24 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id A75F81804D0 for ; Wed, 15 Apr 2020 13:27:24 -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=-1.1 required=5.0 tests=BAYES_00,SPF_HELO_PASS, SPF_NEUTRAL autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS30827 82.113.144.0/21 X-Spam-Virus: No X-Envelope-From: Received: from xdebug.org (xdebug.org [82.113.146.227]) by php-smtp4.php.net (Postfix) with ESMTP for ; Wed, 15 Apr 2020 13:27:23 -0700 (PDT) Received: from [10.219.227.242] (unknown [85.255.232.91]) by xdebug.org (Postfix) with ESMTPSA id 98B1210C24B; Wed, 15 Apr 2020 21:27:22 +0100 (BST) Date: Wed, 15 Apr 2020 21:27:20 +0100 User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable To: "G. P. B." CC: =?UTF-8?Q?Micha=C5=82_Brzuchalski?= ,PHP Internals List Message-ID: Subject: Re: [PHP-DEV] [RFC][DISCUSSION] PHP Namespace in core From: derick@php.net (Derick Rethans) On 15 April 2020 20:36:25 BST, "G=2E P=2E B=2E" wrote: >On Wed, 15 Apr 2020 at 15:51, Derick Rethans wrote: > >> On Wed, 15 Apr 2020, Micha=C5=82 Brzuchalski wrote: >> >> > Hi internals, >> > >> > I hope you're doing well=2E >> > >> > I'd like to announce the PHP Namespace in core RFC for discussion=2E >> > The RFC is authored by me together with George Peter Banyard and >it's >> > purpose >> > is nothing more like to allow the use of PHP Namespace in the core=2E >> >> I think a "may" is not a clever way forwards=2E I think that if you >want >> to use the PHP namespace for engine specific things (like >> Attribute/Token), then they must all use that, or none=2E >> > >Just to clarify is this limited to new features or should this also be >applied to current engine features? >If only the former I personally don't mind making it a requirement=2E Everything introduced for PHP 8 and later=2E I can't think of such an engi= ne related item like Attribute / Token from earlier versions however=2E Can= you? cheers, Derick=20