Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111088
MIME-Version: 1.0
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>
In-Reply-To: <5f163887.1c69fb81.d12d9.299dSMTPIN_ADDED_MISSING@mx.google.com>
Date: Tue, 21 Jul 2020 09:31:35 +0100
Message-ID: <CALKiJKrrkWXyu9hPANc=YM+J04LDcD_CUipQSDUK-_bSgLpqgg@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004c708305aaef74c1"
Subject: Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics
From: rowan.collins@gmail.com (Rowan Tommins)

--0000000000004c708305aaef74c1
Content-Type: text/plain; charset="UTF-8"

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]

--0000000000004c708305aaef74c1--