Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111092
User-Agent: Cyrus-JMAP/3.3.0-92-g11c785d-fm-20200721.004-g11c785d5
Mime-Version: 1.0
Message-ID: <cf427c5a-2e24-4d10-8202-5175196fb135@www.fastmail.com>
In-Reply-To: 
 <CALKiJKrrkWXyu9hPANc=YM+J04LDcD_CUipQSDUK-_bSgLpqgg@mail.gmail.com>
References: <0771c3ac-53ec-4a7f-a4e9-6ae3c9b1f1f6@www.fastmail.com>
 <CALJZF3hy_WqUrzxdEWZVuSutZSvki9RCyd4WN3e+=s1T0+knGw@mail.gmail.com>
 <5f163887.1c69fb81.d12d9.299dSMTPIN_ADDED_MISSING@mx.google.com>
 <CALKiJKrrkWXyu9hPANc=YM+J04LDcD_CUipQSDUK-_bSgLpqgg@mail.gmail.com>
Date: Tue, 21 Jul 2020 07:39:27 -0500
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain
Subject: Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics
From: larry@garfieldtech.com ("Larry Garfield")

On Tue, Jul 21, 2020, at 3:31 AM, Rowan Tommins wrote:
> On Tue, 21 Jul 2020 at 01:36, Mark Randall <marandall@php.net> wrote:
> 
> > So either you fake namespaces e.g. PhpToken or you trample on userland
> > \Tokenizer.
> >
> 
> 
> While you're making a reasonable point, I really wish people would stop
> using that particular class as an example, because I don't think the "PHP"
> in its name is a " fake namespace" at all - it is an object representing a
> token of PHP source code, and thus a PHP token. Even inside a namespace,
> there would be an argument for giving it that name.
> 
> Regards,
> -- 
> Rowan Tommins
> [IMSoP]

To use another, then:

\AttributeDeprecated vs \PHP\Attributes\Deprecated

\AttributeJIT vs \PHP\Attributes\JIT

\AttributeMemoize vs \PHP\Attributes\Memoize

There's a very strong potential for php-src to add a number of attribute classes, which would logically have very generic seeming names.  Getting those out of the global namespace and into a logical organization would be very good.

--Larry Garfield