Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111467 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 54051 invoked from network); 11 Aug 2020 14:44:31 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 Aug 2020 14:44:31 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id F1A241804DA for ; Tue, 11 Aug 2020 06:43:56 -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.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW, 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 mout.gmx.net (mout.gmx.net [212.227.15.15]) (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, 11 Aug 2020 06:43:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1597153434; bh=I4qHqqkka2SI0vD6sZ/mSoEIyJmjKOivjrDsL3J0coc=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=YZudcJimDa5m3F+VQiTKcd3/1QPeDm01+KurMZK4dQdmpqv0WdrxCQDzaSYk/kqC7 D/L+X6HxJuRL2U0ts5HBjEMDEsLVU9RfYPXzFtKt4GGlnPVZFPvSKVzLXLfGIvcczO i4ZBITiruA3XzMqZ89cXBeXcveg7ZyKrq3AZt8GE= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.120] ([24.134.51.41]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MiJZE-1kaj2y1EUY-00fPV6 for ; Tue, 11 Aug 2020 15:43:54 +0200 To: internals@lists.php.net References: Message-ID: <23598724-b141-3b85-b67c-61fed8a1a14d@gmx.net> Date: Tue, 11 Aug 2020 15:44:09 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US X-Provags-ID: V03:K1:Ih6GTRm/hdTt7YcqLiiWNdQAuptE7OoyyffPa11Pr5Jqx/9+LoJ vcGy1YU8JveZJoMitDqrvCTpZP4RxTD1lkQt2m0yaVaq4FnbvLUK8dNm95ZB7YvWOhFBlhu skKiu1B6sGnuy7fQJrr87ZhfaHIlqN+nAeaAx0nav2zZlsycTyF2JInwfjJOUx5Fiw2X6l0 KiHuHwX/rH/eco5A9RLpw== X-UI-Out-Filterresults: notjunk:1;V03:K0:g0BSiGsy3YY=:pVxCwLIZLovP5/nBXhxZVj w3oR+m+YUTQ+CtTtfAUHWb6wJhyMMnXBL+ZR2bJvyNfcK2G/3ZSEAh2QIcTRgBJxd4O+cGjKj iQNi00QZjXvJKS1/BpXBe1VuNJrV6pd1171BAKojWMne9kUOgoa3knsRKT/TF2UKOuNmyPiEU kzPIXB8V3nweIHn/pU+HKE33KEwmHdzikmnuhMxhTXTOOq3C5o9BBGDRemMy1gUQYw1Bv+M/Z jqvKKniMMWIyIUkONR4tG90+izEFiq4K90vp0kXTbiiqp7vaT9uc27Zxk6p1wERFTpFn66G/k rZ8cdAH6pK6zx5+8931ToBHUKhhvtTQH/IomoZCQtW7Xu/5+SgxXQUk3fX+JdcJt0sjDYlt/m mUFDdmg58Xh8KcXmdhbh3MYYh62yhWdQh8Bhx0YhAVxKqagcYBF8DS+UgNwVU9RbPL/vGYsua w3ubbGOOjptvKGlnIw1fuVKSdfHB3+6ZnRZ2ZiKJ/1WYrJHr7dMXoPS4YKwa4d7QUvT2KzDWp /Zi06K1gzyP/sZJtMsaPf/BUXuwuaZ9B9KssnoRCghLFHWD2Zs0fZ8Uo5LMLnPGID/ppfZuT7 MVakBakwqwLBWPSIhFNRfo8SrOeMW5J/q/FzzgYRS06/JUqifr2YIm/YCeJmL6v9Suesmqb+/ F+pA5Ws/rj5S2jeFdujkTyfaVXb/SAutYUPIqq7KAQA7yVvCKEiShseb1xo2meNoHWZ6sPHRB XawdscHEN7f3nm7vgGUq7vSS6Qb2xPOk2amONgFe0NpL4VVtIKL2wRh/YdWyvohBPJ69xp0cN +73HgF6IelTX0ZHXnZO7IakRusJdQBegcr4ubboCaVaiAdbSDAxiTvGnxwpFNQcFA7uNM+Po2 blygbpqubNDxhw+7z8GkyivhgnsndsJlweHvghwsGqYg0tKmECCeelR5RMH0okdwWjU022uC8 BsrI2ppMVhk7lXCpaScX/5Oi4hXGQNMVOD1SyvyAokqeMparewGLAa3jHFijsvNe7pYGzXj0b VzESU1osyGs3yLQNJIgN2owlstHiZoEVnRg3d8JgPIaLo/Se9E0dIxn4s8Nllm8iuibhh03Kz TR68NGC2mcLoRp00mI2Dludr5CjpRclh8DNCEgSTPVZ6eDudeygUePfZR0Viubb2UFKmhlEgV O48uRg4qshYkYC2e38m7brCbbT/IrOUISiiAebtCH6Z9mKqWoMsKw7/T30sDea+q9qQmcMALd iICwWIN5HhBW1moUYs9WQKQvlMNc1HDK9xaJcqQ== Subject: Re: [PHP-DEV] [VOTE] Shorter Attribute Syntax Change From: a.leathley@gmx.net (Andreas Leathley) On 11.08.20 15:15, Lynn wrote: > If typability really matters, we should've deprecated the backtick > version > to run things. We also seem to forget about readability. @@ makes things > really hard to read for me as it draws attention, the same goes for <> > being written as such, with spaces it's fine. In terms of @[] typability= , > my IDE auto completes the ] when I type [. After that we have to type a > word which will most likely require keys on the right side of the keyboa= rd > anyway. Sure, typing @@ is easier, for me this is at the cost of > readability. I read code more frequently than I write it, so I think thi= s > should matter more. > > Please don't use @@ for annotations/attributes. I do understand that not everyone likes @@ in terms of perceived readability, although in IDEs this will probably be less of a problem (by making @@ less noticeable in terms of colors and contrast). It seems unfortunate to me that this RFC just seems super hasty in terms of unfinished discussions and in that it mixes very different concerns - an ending delimiter is made out to be necessary in terms of language, although that seems contentious at best and would be something to agree on first, separate of the actual syntax and how it looks and feels. And if someone does not like @@ yet would like a different syntax with no delimiters, there is no choice for that. The @[] syntax is very last minute, and including the original choice of @: would have also been an option: at the time it lost against <<>>, but after that <<>> lost against @@, so the choices in the RFC are obviously chosen to make sure a syntax with delimiters is chosen, yet sacrificing a proper discussion (and enable people to think about it more) because of the time constraints - instead of just delaying it for 8.1 and having the necessary time to get to the best possible solution. Just compare the previous RFCs about the attribute feature and syntax and the current one - the current one does not even explain the BC breaks the different syntaxes produce, which was otherwise always one of the more important parts of an RFC, so at best the RFC is incomplete in terms of its information. As far as I can tell almost none of the suggestions to amend the RFCs have been taken into account, so the original discussion about it seems to have been pointless. I am a bit disappointed to see this kind of process in PHP, especially "last-minute" before a new major release.