Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111264 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 27252 invoked from network); 30 Jul 2020 14:35:14 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 30 Jul 2020 14:35:14 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 194BC180088 for ; Thu, 30 Jul 2020 06:31:37 -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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, MISSING_HEADERS,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-f174.google.com (mail-oi1-f174.google.com [209.85.167.174]) (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 ; Thu, 30 Jul 2020 06:31:36 -0700 (PDT) Received: by mail-oi1-f174.google.com with SMTP id u24so13838824oiv.7 for ; Thu, 30 Jul 2020 06:31:36 -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:cc; bh=VG7Uf1t3unGZzAp1tTZZ5mtZ4a7/H79cAiaa6mW9y50=; b=Gcbc2t043wH/4uxQWRni0JTohIZ5oZrPuz5GPQeso8FZYzXw6PjJfvmO24Nj0sD8kQ 3GX50f6nj7RsJNAzYUIeckoj4AZ7yL0AXPGKhHY/Mu4tM98RUlCVGlZwZIMe9tZsg7D5 yceZGDe2rqm488ylwPQmZOh8EfMo4CbHeWOIy6VE5ORe34c6BWCfFqltup70lDtxgH05 pZoeqft92PbStx4IEnayAQ1CY2YB3WoBbaHXVDe8yxo5qx2NwZXaK+vBrRI36NDlboMu H3qqocN1QVyL3fJu+/xUFLI8Bakl8w5bZt0BqM3B3eAQQWUAFkPJe0kM59tCcqaGAWZc C7xg== 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:cc; bh=VG7Uf1t3unGZzAp1tTZZ5mtZ4a7/H79cAiaa6mW9y50=; b=sUDszKT2xLmQnUaKwYUvZ17ZHcBrElGCLG92gyiV/JIxveAxUC08GJY1DpTLkIYvg8 Cwz0q4u0QPhEkuszb81ZsUf8vFR35WDU/oHVna3wkjUVxeLFNKm0qEjqBPTB0ceyZT/1 anlP3zGtYqjoTJu+XkZvD7bRBeKo+pMDFbxAGQjlscoc4ZXpE+cAwxoniwKe/u0vx7ag DKvb37dmbIK2ot2OmXibx3RxN0W9GMcHl/H3muoSo3weS/A1qLhsBcRicKtT4iCrJ6e9 3psS5hpl3WxA2Ysr67BIHwyjt/Xbj9LiJCJAgO02pQQ094fUPXHL1W8SraikqRWMRoZv 4OaA== X-Gm-Message-State: AOAM530/RmT6a5KgyIEwW2W5+EvBDdQ47uJpjqD7B68IHC5DZtRULzrT z2S2X/A9f1RVCkCldW0oTUkQ6qThxWMuVxj+brdQpQ== X-Google-Smtp-Source: ABdhPJytzb3VcRO0QI6gXUc90ukbx1uwU6Le+vGTA7+C04xr5oY2IXF5WxBX6vg3WimoCEry9ssBWpYflVvr5+k3HBc= X-Received: by 2002:aca:6708:: with SMTP id z8mr11549559oix.96.1596115894959; Thu, 30 Jul 2020 06:31:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 30 Jul 2020 10:31:23 -0300 Message-ID: Cc: PHP Developers Mailing List Content-Type: multipart/alternative; boundary="000000000000f0833305aba8b020" Subject: Re: [PHP-DEV] [RFC] [Discussion] Shorter Attribute Syntax Change From: david.proweb@gmail.com (David Rodrigues) --000000000000f0833305aba8b020 Content-Type: text/plain; charset="UTF-8" I would like to suggests the syntax "using attribute(Attribute, ...)". It is more clear and should not create BC. Em qui, 30 de jul de 2020 10:28, Joe Ferguson escreveu: > On Thu, Jul 30, 2020 at 7:50 AM Benjamin Eberlei > wrote: > > > I think it has become clear that we need to revisit this syntax question > > again, including the elephpant in the room of delaying this feature to > 8.1. > > > > The reason is not only Joe's desire to revote on #[], > > > > > No, I *do not* want to revote. This RFC simply takes a formal approach to > approve the syntax that came in 2nd based on concerns raised with the @@ > syntax. > > Now that it seems the technical concerns around @@ have been resolved by > another pending, passing, RFC, I'm still here wanting us to talk about the > impact of @@ on static analysis tools. Apparently, internals doesn't care > about these projects. I care and I'm trying to help. I'm not trying to > revote until I get the vote I want. I'm just a dude that had some free time > while on vacation when he saw a chance to contribute. > > I see two possible outcomes: > > Release Managers collectively should decide what we do to move forward. > Either accept @@, we'll decline this RFC and we can move on to the next > nearest bikeshed. > > OR > > If Release Managers don't want to, or can't collectively make a decision > then this RFC should go to a vote and we'll see what 2/3s of the group > want. > > I'm fine with either outcome. > > https://wiki.php.net/rfc/shorter_attribute_syntax_change > > -- > - Joe Ferguson > JoeFerguson.me > osmihelp.org > --000000000000f0833305aba8b020--