Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110637 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 3863 invoked from network); 17 Jun 2020 23:21:05 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 17 Jun 2020 23:21:05 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 0173D18054F for ; Wed, 17 Jun 2020 15:06:53 -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=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS48854 94.231.96.0/20 X-Spam-Virus: No X-Envelope-From: Received: from smtp.simply.com (smtp.simply.com [94.231.106.220]) (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 ; Wed, 17 Jun 2020 15:06:52 -0700 (PDT) Received: from mail-wr1-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by smtp.simply.com (Simply.com) with ESMTPSA id 49nK0q4F3Nz63YD for ; Thu, 18 Jun 2020 00:06:51 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=givoni.dk; s=unoeuro; t=1592431611; bh=MOrZd0nQwTnRvizw/4Qc/S3vF6rFnH1gPN7nB4AXvzw=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=iWgg+JrBwWGA2EByahX6qxgKT5GsnIzRGVTMprXPVh9Sj8/wLhh6e89jFFTAWClnv xIITx86CC433rzizKTAMYRIXTK25PsVoz81ujuSFQ3jVGTlEaO8JY0FfRbexmXBjVo cVc7MdGFo8Kz3nKZu03yksCFRfuJg0Bi5hNQ6PFY= Received: by mail-wr1-f42.google.com with SMTP id r7so4012381wro.1 for ; Wed, 17 Jun 2020 15:06:51 -0700 (PDT) X-Gm-Message-State: AOAM531F1Z0eX69BGATd8XJFTvuJbkJxUwzr1HHO7Ffy+lo+V/ej/Kmd zfRh7NCE4JXLpjwrfePWJWF2/g8U74tTSQFxb7A= X-Google-Smtp-Source: ABdhPJymiyCyRt8O89Wa0haV+oUfzKr/wgjhPqe8Sl4KXJ5WYBgC5GIh812fMyJIfDoFgG8nSskgolSplFuoElKsoAs= X-Received: by 2002:a5d:498f:: with SMTP id r15mr1377228wrq.175.1592431611106; Wed, 17 Jun 2020 15:06:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 18 Jun 2020 00:06:40 +0200 X-Gmail-Original-Message-ID: Message-ID: To: Nikita Popov Cc: PHP internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] [RFC] Treat namespaced names as single token, relax reserved keyword restrictions From: jakob@givoni.dk (Jakob Givoni) On Tue, Jun 16, 2020 at 10:52 AM Nikita Popov wrote: > > Hi internals, > > Inspired by the recent discussion on reserved keyword reservation, I'd like > to propose the following RFC: > > https://wiki.php.net/rfc/namespaced_names_as_token > > This RFC makes two related changes: Treat namespaced names as a single > token, which enables use of reserved keywords inside them. And remove > reserved keyword restrictions from various declarations. > > 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. > > Regards, > Nikita Love it, thanks Nikita! In a mail that probably went to everyone's spam folder, I asked for opinions on allowing use of .\Foo as an alternative to Foo in the current namespace, thus reducing friction with reserved keywords even more. Any thoughts on that now? Best, Jakob