Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109750 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 29585 invoked from network); 21 Apr 2020 13:04:02 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 21 Apr 2020 13:04:02 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 912891804CE for ; Tue, 21 Apr 2020 04:35:27 -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-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-wm1-f65.google.com (mail-wm1-f65.google.com [209.85.128.65]) (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, 21 Apr 2020 04:35:26 -0700 (PDT) Received: by mail-wm1-f65.google.com with SMTP id r26so3302148wmh.0 for ; Tue, 21 Apr 2020 04:35:26 -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=LPqnXZMS6ldAZVJyBnNhbY+kdKQOFsM/dos4EgmwtOk=; b=EQUn2oMDPDHFY5OpU1DO4J8idWk7/UU9sSKbSVWi0SdXhaKDOIedwxX0G85lWcjZ5p AEdbdEwSXDOB0E63IjaU9xB3R2RYAn5H2cf/ewPSh7HYIo1odUSCDjDNYHQr26Kz3+Uu R29lyioGlOqsSMofzM7EYb5KFY9/8vKAKBQyFp4lP2lgE2HFIz2GQGwIHxmNEKp2DjNu Utc65EpvhwsSkdD0lTtt2d4iyywwUsbnlJuA+FXRipAblc1/rfMSbouRy3JjaJMta6j+ G+ByZwKLj40TmYfQV+/jQnp8o4TeoynUwzG8hYTxtLkpcmMhIOmKzfT052NkFd/N4Qs5 bFKg== 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=LPqnXZMS6ldAZVJyBnNhbY+kdKQOFsM/dos4EgmwtOk=; b=b+MJ4rF8rCPO58Eo+rjOPQV+uKxpAIozUR9W1UC41eAsye8QMZCjk/FX4gxbaC/+3O vnh3ymXZceQIbnUcWB6VtBJVwOvoEi5QDGaJIgfUNDJ8f1ZBYSj+kIQ3aHV951QAUjQz u71Nq7bbSRy41yDUabzn7Ft9Y2a95Ws6fGjHNw7Lv5ZTyUURxQ8zrffyQUGGPQeJ9Uvp rU+4nd3EnRMhMU4t7fyHmGZgwp9s5kFBSSAn61GvJez7nrd8c6MdBuFwNr0BDVixpLSh hfVes4pU0/uYMjqHEdHooD78C+rqIXrGR8bQ2YZC+HrjIn/PWjX2diBgfcV5SVlvmOvL ntNw== X-Gm-Message-State: AGi0PuZn9M+TtLjA2suk4DVAGA3ibfC1l4Jl4JtI4Nymz7a9eiS0Kz37 evpH6wczbHI5aDX08kKIjvWrKFFU1i8iZc+Rc0W5fg== X-Google-Smtp-Source: APiQypKytvitnuDYVMCK6ldViwk7HKAMwJKspJ8ogHO2Xn7awXlazyhrZcuKmp9POcxgfapCarJDfdq0wQPPwhe7+/I= X-Received: by 2002:a1c:4946:: with SMTP id w67mr4694359wma.38.1587468922825; Tue, 21 Apr 2020 04:35:22 -0700 (PDT) MIME-Version: 1.0 References: <5e9e1335.1c69fb81.9a507.b80cSMTPIN_ADDED_MISSING@mx.google.com> In-Reply-To: Date: Tue, 21 Apr 2020 13:35:11 +0200 Message-ID: To: Peter Bowyer Cc: Peter Cowburn , Marco Pivetta , Andrea Faulds , PHP Internals List Content-Type: multipart/alternative; boundary="0000000000003cc38305a3cb697e" Subject: Re: [PHP-DEV] Re: [VOTE] Attributes v2 RFC Vote is open From: kontakt@beberlei.de (Benjamin Eberlei) --0000000000003cc38305a3cb697e Content-Type: text/plain; charset="UTF-8" On Tue, Apr 21, 2020 at 12:39 PM Peter Bowyer wrote: > On Tue, 21 Apr 2020 at 09:15, Peter Cowburn > wrote: > > > I know that I'm "too late" to be making suggestions, but I would like to > > see > > a new "@@" operator over the proposed <<...>> or @:. > > > > I support this, and agree with Theodore Brown's earlier message ( > https://externals.io/message/109713#109717). > The discussion on this RFC was 5 weeks and the syntax suggestions until yesterday have all been suboptimal. While the nerd reference of a potential AT-AT operator gives me tickles, same with the now included smiley alternative @: these approaches have the downside that they don't have an end token, and are therefore visually "harder" to spot on declarations (subjective impression). It is my belief that even with @@ as secondary alternative the <<>> syntax would still prevail for this reason. I remember reasonably well how internals exploded when the namespace operator was selected, everyone was making their own appeal to the syntax gods for something different. Please be reminded how this is the 7th RFC on attributes in PHP and on many of the previous ones the problems came down to syntax, except the Attributes v1 where <<>> was proposed as well and the implementation (exposed ast\node, no namespacing) was the primary reason for it getting rejected. > > Peter > --0000000000003cc38305a3cb697e--