Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110245
MIME-Version: 1.0
References: <CAEPJdum6xCwABjpor1YYvuosSB1dEb4xnCZEMABKsEEvNXvcQQ@mail.gmail.com>
 <CAF+90c_QNBU-cc_3g7wrCFb8b_FbGR-hOFs2XOk1aJdTsXh=Ag@mail.gmail.com>
In-Reply-To: <CAF+90c_QNBU-cc_3g7wrCFb8b_FbGR-hOFs2XOk1aJdTsXh=Ag@mail.gmail.com>
Date: Fri, 22 May 2020 12:55:44 +0100
Message-ID: <CAJvSBVNcECz0B2fx+LBXW34rnw3bYcqcpFn1LfjNBkiV9+b7bg@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: Benjamin Eberlei <kontakt@beberlei.de>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000041217205a63b5122"
Subject: Re: [PHP-DEV] [RFC] Amendments to Attributes
From: phpmailinglists@gmail.com (Peter Bowyer)

--00000000000041217205a63b5122
Content-Type: text/plain; charset="UTF-8"

On Fri, 22 May 2020 at 12:09, Nikita Popov <nikita.ppv@gmail.com> wrote:

> While I'm happy with "Attribute" living in the global
> namespace, I don't really think we'd want to introduce "Jit" as a class in
> the global namespace. The name is simply to generic and does not indicate
> that this is part of the attribute system. We'd be forced to go with things
> like DeprecatedAttribute or JitAttribute, which seems rather non-optimal to
> me, as we're just reinventing namespaces to avoid using them...
>
> As such, I would suggest to introduce a common namespace for all attributes
> provided by PHP. This means we'd have Attributes\Attribute,
> Attributes\Deprecated, Attributes\Jit, Attributes\NoJit etc. (I'm also okay
> with the PHP\Attributes\Deprecated variant, but that's a separate
> question).
>

This is the best real-world argument in favour of PHP namespace in core
that I've heard.
https://wiki.php.net/rfc/php-namespace-in-core

If we don't want to introduce classes in the global namespace, it makes
sense to have a reserved PHP namespace we use.

Peter

--00000000000041217205a63b5122--