Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111550 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 12936 invoked from network); 16 Aug 2020 09:28:31 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 16 Aug 2020 09:28:31 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 9A58A1804DA for ; Sun, 16 Aug 2020 01:29:08 -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 ; Sun, 16 Aug 2020 01:29:07 -0700 (PDT) Received: from mail-wm1-f51.google.com (mail-wm1-f51.google.com [209.85.128.51]) (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 4BTr1Z2KSTz60vL for ; Sun, 16 Aug 2020 10:29:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=givoni.dk; s=unoeuro; t=1597566546; bh=LIatjBbpS8ncBqCnOqF6UkUUVjqCIn61vb7dE5QgM7I=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=NT0FSRu1Dv0wjs+8R3sNmocuxYj3wVqAJKGc6daDAl7LBCVM3maZD9Xl4Is21+BJP CVSzy58KM7mKHmFb7YXMKH7vc9t9zvn7LrGmbysl0Z7iU/CiMP3YzJARmIbNFvhRwZ pviGddXXapfTRocnTVAT4WtgqGqZauEXA7rcR28s= Received: by mail-wm1-f51.google.com with SMTP id 184so11419256wmb.0 for ; Sun, 16 Aug 2020 01:29:06 -0700 (PDT) X-Gm-Message-State: AOAM533zEB656bFAvZQEtByCqJ4+TXkJAHfxr0b+53+HFZz6ELD4aULx WbcbCce2x+A8pmtl1ozhQMODG8L654wKey0XA8Q= X-Google-Smtp-Source: ABdhPJwGPB8CS2y/fyip+C/0/PzlOrvXaeyREQksvUHADK0rRWLXr+ElggGGknzL94aqFIwAYMAjQBaa88B3Ya9wsho= X-Received: by 2002:a1c:e304:: with SMTP id a4mr9770656wmh.11.1597566545951; Sun, 16 Aug 2020 01:29:05 -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: Sun, 16 Aug 2020 10:28:54 +0200 X-Gmail-Original-Message-ID: Message-ID: To: Benjamin Eberlei Cc: Benjamin Morel , =?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) > > Can I make a suggestion? > > Make the new or updated RFC a primary vote on: "Should attributes be > enclosed in delimiters?" Actually, let's add the word "block" in there: "Should attributes be enclosed in block delimiters?" Where block delimiters are "matching" (not interpreted in any strict way) beginning and ending symbols. This is in opposition to f.ex. the @@ syntax that does have ending delimiters (you know that it ends when you find a specific token), whether they are a closing bracket or a white space. So the question becomes "block syntax" or "non-block syntax". Best, Jakob