Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111483
MIME-Version: 1.0
References: <alpine.DEB.2.23.453.2008100935570.7489@singlemalt.home.derickrethans.nl>
 <CABHuAWyyNQ-w8X458OCbQxX5WXLwABhFjv8sFEbwcw1YrG=rhw@mail.gmail.com>
 <alpine.DEB.2.23.453.2008111320530.7489@singlemalt.home.derickrethans.nl>
 <CABHuAWx_rF=_o7UXmzexKPtzbj_vFRa8sodSOMhe5tS1rtvLiw@mail.gmail.com>
 <BYAPR05MB65351C2A1E0F10B01739DE32DE450@BYAPR05MB6535.namprd05.prod.outlook.com>
 <alpine.DEB.2.23.453.2008111429150.7489@singlemalt.home.derickrethans.nl>
 <BYAPR05MB65355C3C5955E5CC83ACC0F1DE450@BYAPR05MB6535.namprd05.prod.outlook.com>
 <CALKiJKrs2T0M8adZLsEDWsO+oFXv3DoTi1_aLhFfCOGOsrX+=A@mail.gmail.com>
 <BYAPR05MB65357A2EC875D4DBEF73D3C4DE450@BYAPR05MB6535.namprd05.prod.outlook.com>
 <CALKiJKpN2j76iXbF72_tL+j4KEqgNGYm2ZCvt_DxfiorStTG8w@mail.gmail.com> <BYAPR05MB65358BD9253C8AF1986B7934DE450@BYAPR05MB6535.namprd05.prod.outlook.com>
In-Reply-To: <BYAPR05MB65358BD9253C8AF1986B7934DE450@BYAPR05MB6535.namprd05.prod.outlook.com>
Date: Tue, 11 Aug 2020 18:10:45 +0100
Message-ID: <CALKiJKpexcxdC7HMrMG1JeFuPbUXWDRwDvkBYBoRNtHZxkw--g@mail.gmail.com>
To: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a58d5705ac9d2790"
Subject: Re: [PHP-DEV] [VOTE] Shorter Attribute Syntax Change
From: rowan.collins@gmail.com (Rowan Tommins)

--000000000000a58d5705ac9d2790
Content-Type: text/plain; charset="UTF-8"

On Tue, 11 Aug 2020 at 17:54, Theodore Brown <theodorejb@outlook.com> wrote:

>
> I think you may have misunderstood my point - it's not so much about
> the leading symbols but about grouping.



That sounds like a reason to vote No to grouping, which you already did:
https://wiki.php.net/rfc/attribute_amendments#group_statement_for_attributes1



> What will you grep for if you want to find all places where the Route
attribute is used (but not some other class named Route)?

With any syntax, you can't exclude other classes named Route which are also
being used as annotations. If you want things to be easy to tell apart,
don't call them the same thing.

If you specifically want annotations to stand out, name or alias all
annotations as "RouteAnnotation" or "ARoute" or something.

For that matter, just make a coding standard in your project to never use
grouped attributes, or always use fully-qualified names in attributes...


Regards,
-- 
Rowan Tommins
[IMSoP]

--000000000000a58d5705ac9d2790--