Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111543 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 46796 invoked from network); 15 Aug 2020 22:46:54 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 15 Aug 2020 22:46:54 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D1CCA1804D2 for ; Sat, 15 Aug 2020 14:47:23 -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,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from smtp.simply.com (smtp.simply.com [94.231.106.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 15 Aug 2020 14:47:22 -0700 (PDT) Received: from mail-wm1-f52.google.com (mail-wm1-f52.google.com [209.85.128.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by smtp.simply.com (Simply.com) with ESMTPSA id 4BTYn50yJ7z622t for ; Sat, 15 Aug 2020 23:47:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=givoni.dk; s=unoeuro; t=1597528041; bh=S8jSs0I+iJ/Addky5DiXUxKnA5RilNEt0x5ilIprzos=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=hnHt2j4wZTHPh/3/y/poi8u0Md1D+W+GC/tHjW8htxzQI36sHDRBxpTov0fTZo/7S +O2ClipRg+zoEHYSShZ/vR2O/yE3fbLUiPe8WrEl0uu2I9q23/M3it4JhrAfQzh6t7 XZljLqq9WIP6OuOu5F60/6QShN5SQmrOF8J5Enzk= Received: by mail-wm1-f52.google.com with SMTP id k8so10803673wma.2 for ; Sat, 15 Aug 2020 14:47:21 -0700 (PDT) X-Gm-Message-State: AOAM533EtW1FgU0gHzE/ruvL0KRyqX6jReq/CT0OSB809meXchRsXKoh l0EJFbFse1m7DB6cpxWdKa5LUDh3CePuZgG4Bs0= X-Google-Smtp-Source: ABdhPJy2Zun1v1DLy7odLRq8GXfdlHfHuubNm08B1/BW+M6kmLCH3qAQY+reIaKTpZNl264jR0tDIn7uTV82EhW1K2I= X-Received: by 2002:a7b:c185:: with SMTP id y5mr8255869wmi.95.1597528040658; Sat, 15 Aug 2020 14:47:20 -0700 (PDT) MIME-Version: 1.0 References: <5cc837df-ab47-628a-d29b-46d7933be973@gmx.net> <3A7CECC3-CDEE-4852-BF4B-4EC7CA1BD538@pmjones.io> <7d6c42a4-53cd-5e38-4ffc-02fe490d66a3@gmx.net> In-Reply-To: Date: Sat, 15 Aug 2020 23:47:09 +0200 X-Gmail-Original-Message-ID: Message-ID: To: Benjamin Morel Cc: =?UTF-8?B?TWljaGFlbCBWb8WZw63FoWVrIC0gxIxWVVQgRkVM?= , PHP Internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] [VOTE] Shorter Attribute Syntax Change From: jakob@givoni.dk (Jakob Givoni) This will probably be my only contribution to this thread so I'll keep it simple: Am I in favor of a revote? Yes Can I vote myself? No Do I think a revote will change anything? No Have there been any good arguments for why attributes need an ending delimiter? No The RFC says that > The main concern is that @@ has no ending symbol and it's inconsistent with the language > that it would be the only declaration or statement in the whole language that has no ending termination symbol. However, it's clear that attributes are neither a declaration nor a statement, but metadata about the thing that follows them (unless it's more attributes or comments). The ultimate proof of this is that a semicolon after an attribute is illegal. Do I think attributes need an ending delimiter? No Would I prefer the @@ syntax? Yes Do I think @@ is ugly or difficult to type? No Is it just a subjective matter of personal taste? Yes Is this whole discussion almost entirely a subjective matter? Yes Is this email thread, the RFC, the voting and the discussion about extending it a farce? Yes Do I mind waiting until 8.1 to have attributes so that it can be done right? No Godspeed! Best, Jakob