Re: Re: [RFC] Treat namespaced names as single token, relax reserved keyword restrictions
| From: | Peter Bowyer | Date: | Thu, 16 Jul 2020 08:13:19 +0000 |
| Subject: | Re: Re: [RFC] Treat namespaced names as single token, relax reserved keyword restrictions | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-111039@lists.php.net to get a copy of this message | ||
On Thu, 16 Jul 2020 at 09:04, Nikita Popov <nikita.ppv@gmail.com> wrote:
> While I don't think anyone had plans to mix whitespace, this is indicative
> of a larger issue. While I'm one of the people who voted for @@ as my first
> choice before, I wouldn't do so now (even with this RFC accepted). This
> issue made me realize that there is more at stake here than just "which
> syntax is prettier?" and choices that have a "closing tag" are technically
> more favorable, especially if we consider future extensions of the
> attribute system that may introduce additional ambiguities (e.g., Rust
> allows placing attributes pretty much everywhere in code -- how sure are we
> that there will be no unanticipated ambiguities?)
>
Thanks for this clear explainer. I hadn't appreciated the "no closing
delimiter" issues during the original vote, also picking @@.
As many other languages use '@' as their symbol, how do they handle or
avoid the whitespace issues?
Peter