Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110649 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 82637 invoked from network); 18 Jun 2020 09:18:46 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 18 Jun 2020 09:18:46 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 86C4C1804C8 for ; Thu, 18 Jun 2020 01:04:36 -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 ; Thu, 18 Jun 2020 01:04:35 -0700 (PDT) Received: from mail-wm1-f43.google.com (mail-wm1-f43.google.com [209.85.128.43]) (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 49nZGT3dtFz61Z0 for ; Thu, 18 Jun 2020 10:04:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=givoni.dk; s=unoeuro; t=1592467473; bh=99oc709RNZnIgezzOMsC3A4H+vY91r2x3uq1VupUxnw=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=qZc0aNnPU8aeXTj0ELCRTmD8+pK8k8HUMfoicQaFyIVPuqRT18arSnaIERO89p3Zb mWyw30b+Urcrb2711B7EzJcN2PnbtKfpITqC4E+jO7m+/6HoSfiJNKDpF2D/jnl0cY zd+sMUqVVVFxhB3IvNAzuhcZpFeGdh6nKPmFpK74= Received: by mail-wm1-f43.google.com with SMTP id f185so4627981wmf.3 for ; Thu, 18 Jun 2020 01:04:33 -0700 (PDT) X-Gm-Message-State: AOAM532nRYlx9xsV6RdyT5G/jL7KSBFbg8ZUIJMLqbWqlOpAidtSzo8T UMKgr4hRA43mXcvQzxz7y4c+Z7Vkjhl5pOcwcvA= X-Google-Smtp-Source: ABdhPJxbiHzwB7KDQaLVLVlqDkPnGxtD3nqwAiNP31kTTe3/4pmd7IZrzzmxtboSZiX04jsmhV2P1y792EuUEtyF4qQ= X-Received: by 2002:a7b:c249:: with SMTP id b9mr2520218wmj.143.1592467473114; Thu, 18 Jun 2020 01:04:33 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 18 Jun 2020 10:04:22 +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 Thu, Jun 18, 2020 at 9:39 AM Nikita Popov wrote: > >> 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? > > > How would .\Foo be different from the currently existing namespace\Foo? (Note that "namespace" here is to be taken literally, not as "put the current namespace here"). > I didn't know you could do that! I don't think I've ever seen it used, maybe because there's been little advantage over just Foo? I guess it only matters if you also import Foo? For what it's worth, .\Foo would be significantly shorter than namespace\Foo and probably more intuitive to understand as well. Furthermore, if you were to create a namespace called "Namespace" (don't judge! ;-)), which I would assume would be possible should this RFC be implemented, we could avoid namespace\Namespace\Foo :-D Thanks for the feedback, it was just an idea - could be a new RFC some other day. Thanks, Jakob