Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111235 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 24895 invoked from network); 28 Jul 2020 21:50:54 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 28 Jul 2020 21:50:54 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id CD9D8180510 for ; Tue, 28 Jul 2020 13:46:52 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-oi1-f180.google.com (mail-oi1-f180.google.com [209.85.167.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 28 Jul 2020 13:46:49 -0700 (PDT) Received: by mail-oi1-f180.google.com with SMTP id w17so18761010oie.6 for ; Tue, 28 Jul 2020 13:46:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=73OsLCG1wb76wlYbQowD2wWDT9EI1Rkuvz1JNG208TE=; b=OAZS6c45qkgo2YFAO/MaCAMVsorC9yJ3wNQQ/u72WACmklOWH4OOKZAJJBBLWocYcQ wzr0BXLfiX0scqzvTmB4PokqFb1MLB1aeSIFgF4C1bzQZIhMwSqIja3/p84R+N8A4HMY TpE2MYqbU/kp68eErLW0jvrDSz7DzrZU/cdt7M91pGrMlTOc9Ni7Wqh8HG5AbJyjhl9E cdG7WE1QxjE/hC2p5V1fj6PJJDXk/05Tt6GX9UYCYUrVRY4JQWbjHTxL5CuFN0RH9e0t kMajr4voQPu7O58lsR9/IivlsLyFAxmIrEIdusGCrkBgBlJ7VG71qkRr/U18NBE9lOPt qijQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=73OsLCG1wb76wlYbQowD2wWDT9EI1Rkuvz1JNG208TE=; b=e//Ze+a1Y0C9CCGMmXeN4Pd5jt0oI+/JS5YjjERnMZW2Nu5OKdMi7gY7RyTV8IvEMM RL1aUiKLSim1J8xGKyLIfEzDCB+OtUuIav3f5lkB47kWelxstJ9VP0BubFXJts8R9xcR wJPoH9vN1ndK1/F+FpeW+TySGLi591MhUWVL3gtnAaVF6l367oCvYF5NHJSzu0MQ5vAk 2VaIhfF7M7uwqoYfxstI1GX5B0hRgObkGnfMveSmUrMqlwy2dMm6dB6w82usjNL2vmSK Qcs2XV7HiozRgjZZsC/XWdIDtUv/HAAq+gRoKBJ0p+IQSAwSE8+odKjMsV0ghRf4BZsk gOFQ== X-Gm-Message-State: AOAM5316kg2+/RDGJc2u7RIrVlfIAruhRg0jMOZUog6yzjTyYmFvp7Pn LTTMXmOX2e41h0Kz/D16CjrqJX0HvznGOAOkMAU= X-Google-Smtp-Source: ABdhPJy6TztXWdfNjyZo4Nv7xvDxBlerfG2uZsR+AAi5NRcSMKgVlju2xUoZ/oz+TjJDrUJk9gyO3hGhr8x6ClRTBew= X-Received: by 2002:aca:171a:: with SMTP id j26mr5360634oii.92.1595969206934; Tue, 28 Jul 2020 13:46:46 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 28 Jul 2020 21:46:10 +0100 Message-ID: To: Marcio Almada Cc: Joe Ferguson , PHP Developers Mailing List Content-Type: multipart/alternative; boundary="000000000000a6e0e205ab868955" Subject: Re: [PHP-DEV] [RFC] [Discussion] Shorter Attribute Syntax Change From: petercowburn@gmail.com (Peter Cowburn) --000000000000a6e0e205ab868955 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable (Top posting because... sue me.) I hereby propose to use @[] syntax for attributes. No need to vote; it's clearly the best, nay only, real option. Make it so. P.S. Sorry for suggesting @@ earlier, I've no idea what I was thinking. Creating new syntax is HARD! P.P.S. <3 On Tue, 28 Jul 2020 at 20:59, Marcio Almada wrote: > Hi, > > > > > On Tue, Jul 28, 2020 at 12:57 PM Theodore Brown > > wrote: > > > > > > > > Hi Joe, > > > > > > From the perspective of looks alone I don't care much one way or the > > > other between @@ and #[]. However, I don't find the arguments for #[] > > > in this RFC very compelling, and it ignores some of the other downsid= es > > > of #[] compared to @@ that should be highlighted. Let's go through th= e > > > arguments from the RFC: > > > > > > > > > > > Theodore, thanks for your comments, time, and work on the Shorter > Attribute > > Syntax RFC. I appreciate your feedback and I'm also of the mind where I > > don't care based on looks alone. The RFC also notes the @@ issues have > been > > resolved by the RFC closing at the end of the month. > > > > My motivation for this RFC is based on 2 things: > > > > Firstly, the @@ syntax makes parsing harder (although not impossible) o= n > > CLI tools such as PHPCS. Therefore IMHO internals should make the best > > effort to avoid this when possible. > > > > Secondly, I'd like to see internals use this as a point in the future t= o > > avoid this kind of issue where we need to vote on something yet again > > instead of taking the runner up in a ranked-choice vote. Originally thi= s > > was my main motivation until I saw the issues raised by the PHPCS users= . > > > > Is this issue documented somewhere on github or on any other platform? > I'd like to see the discussion and maybe participate in it. > > Thanks, > M=C3=A1rcio > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php > > --000000000000a6e0e205ab868955--