Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111578 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 47516 invoked from network); 17 Aug 2020 13:28:45 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 17 Aug 2020 13:28:45 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 9F760180089 for ; Mon, 17 Aug 2020 05:29:40 -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=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-wr1-f52.google.com (mail-wr1-f52.google.com [209.85.221.52]) (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 ; Mon, 17 Aug 2020 05:29:40 -0700 (PDT) Received: by mail-wr1-f52.google.com with SMTP id a14so14807449wra.5 for ; Mon, 17 Aug 2020 05:29:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=beberlei-de.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=s0+W4YTfjGCy6Zniro4znNjvJMCpR7TM949Im4KHbVA=; b=naS51W7WK+uhAHYpT0OmjzrvWpuPbqzhHNgWZFp1GtC0ddUiLmupiwH5p4LPSbTYNT 9pNfTYJnXy6HINCr91o+kOm4LRjk4TFvsH27DvWlr+ZRfHLmqFcxhC0TGnxksUKI1zxq bDFlM9608sOGK+DOZ7N1000w12UEtXp2As95OJbWo2wuDiNkVHn7ImdzJcQsjAfAYcSI F4oiJ5DAHsmg7KbSocRpTkTSXWtqaGCXw4isoX4Epwe7JAgFIJJB5RNGhxWbr5K5WpZ3 2BmR6N7wZTfGkChKMQMC1MjRGoPcr6znpltBFwrgSZuvgWUc/xmQQ3Pv2BJeSXiW68/N IWWw== 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=s0+W4YTfjGCy6Zniro4znNjvJMCpR7TM949Im4KHbVA=; b=B/bfN6aEcgfXjJheq+X00BrAOnQqpfBYRBZD/bVIUwU6h5o1wV2WNfEPzpyV7sQSgt l2b4pfqCOTjhqwEbC4ZEV33/r2oc56gpZreCOQAVJci+atdNvbuv0FVpiFtKnYcAEWTH VW0AgWiF06UYM2LVGkieZt+HSolIYyeOsU7wggIgOUTM7FGdkO9fEs3Rd+KhC8VGmI8v IIGs3am1cGpjhMTZRAX33j/pmL7E7wwMDTYCwWrC1ANTsO7yA/OQqoysi9VF3DuFFChl +lE7NNlV5O9dgsVaCxMsfNAtNQ4OKEyYr5q/oq/DKdr4eDfdNAtCqK4pWjSCIAONgy/q JEEA== X-Gm-Message-State: AOAM530bNUbk14ccdGVtKhdAwfIsxH2W5H7tWmzIoVQ6u16AQe2f6yY5 vCsNJgwScS5MihGDq8XZm9iAzc0k2WJvDggbvMhpkDNILbULgg== X-Google-Smtp-Source: ABdhPJz4i0I+AEQg5TLYxLgD6QAGIwdv60Yw2VvyLe43yvgvs1CvwuMFGu8APagKJygSYypQ0thP4hQeX8UJYRD/x54= X-Received: by 2002:adf:dcc8:: with SMTP id x8mr16020838wrm.16.1597667379421; Mon, 17 Aug 2020 05:29:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 17 Aug 2020 14:29:28 +0200 Message-ID: To: Peter Bowyer Cc: Derick Rethans , PHP Developers Mailing List Content-Type: multipart/alternative; boundary="0000000000009eb00f05ad11ecd4" Subject: Re: [PHP-DEV] [VOTE] Shorter Attribute Syntax Change From: kontakt@beberlei.de (Benjamin Eberlei) --0000000000009eb00f05ad11ecd4 Content-Type: text/plain; charset="UTF-8" On Mon, Aug 17, 2020 at 10:02 AM Peter Bowyer wrote: > On Sun, 16 Aug 2020 at 10:29, Benjamin Eberlei > wrote: > >> We have updated the RFC at >> https://wiki.php.net/rfc/shorter_attribute_syntax_change with what we >> think >> covers all the discussion and arguments made in this and the previous >> mailing list threads. >> > > Thank you for putting in the work it took to revise the RFC. It's good. I > now understand what the delimiters achieve. > > While I don't agree with the first point in "Forcing @@ Attributes to end > with parenthesis does not solve issues" (in this new syntax I'd ban > whitespace) I appreciate the point you are making, and it is sensible for > consistency. > > I feel grep'ability has been played down, as unless > @@ > MyProject\FooAttr > > is allowed (which isn't shown in the codeblock), then it's easier to grep > for @@.+?Foo and know you have a chance of an accurate match (assuming > renaming is not used) than it is with the delimiter syntax. > no space is allowed between @@ and name, they have to be in the same line. The whitespace between name and argument_list is not currently banned, the comparison is to the status quo (since that is not expected to change). Still I think the grepability has to rest on no assumptions, because otherwise you could argue the same for @[] being used non-grouped on one line and would have to conclude that this is also grepable. > > Sorry to everyone for causing this hazzle. >> > > These things happen. Thank you for taking on-board the feedback and > working on the RFC. > > Peter > --0000000000009eb00f05ad11ecd4--