Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110765 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 7759 invoked from network); 29 Jun 2020 08:20:13 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 29 Jun 2020 08:20:13 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 677A01804C2 for ; Mon, 29 Jun 2020 00:08:51 -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,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS 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-ed1-f51.google.com (mail-ed1-f51.google.com [209.85.208.51]) (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 ; Mon, 29 Jun 2020 00:08:50 -0700 (PDT) Received: by mail-ed1-f51.google.com with SMTP id d16so5247002edz.12 for ; Mon, 29 Jun 2020 00:08:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=YK9iGXde341gKQ3qAmaUu7nvauIEz0AGDAQRJIofDmg=; b=DCgc1/yeVJO2VDvfkuZYuo+0uAgWU1H3oeaHnOh0FNiyaQqLkGtG+/Pqlprp01u2li KTIoEFO1viPif2Hrt4vTr/NCyqn/El+wawA39HH5cJckVrlPHIM0riKA2z5fXQ3Bqo6V U0ivP/G6mghBrqw2nQPfdBkgAAptrVEop2A9QiUfZQPCz95ETDrL7KsVNWf5IYV5R8Ax 7Y3RPBG0ygJ3DQ2vRRW7zdkED10W6AIzILtTxPDlVPT79+Ftfw7ETnYEY4CVSHPpIEv9 T96q0PyXE+8d6vy/zpiho9Ll2ntCd7ZRuqJV2WzVhJlLlXj/IpXx/rciZhoAvNVqGgeb eQ7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=YK9iGXde341gKQ3qAmaUu7nvauIEz0AGDAQRJIofDmg=; b=iTlg/CYzIENN5FpJFouhgTgguMoa+rTgW+MU+Ebycr+LL4iiAfOl107wXJESpFVKM5 tgLvC33PTEBltDCuaYxjGsqi7Rj1QZ/Fj7M1XdlQFvAVcAp8GjvJto9U+5+nVii+UBsZ diFFR+ZBDTZ4W3QOk1eNcjM8uDgPZx/wHjAg/dmi95BTOtyVDB7orzN8Q8ITUf0QkaEw zB8Vt4Sj9l7mMFCftniE4GnIHlR6LYGYBOrHVL8BDP0aSps2GmJ4EP4lG5BY6ckVJOLZ ZvQOcEag8vLSc4gsT9OrtWYuV0s/VUSzVygeZi5f1aR1kI0USbMWMCyM/hnxMy0xV2Dv P9jw== X-Gm-Message-State: AOAM530PoPZAdBOu7iBViNNs+X2Ez1xniAlH8K5grQoMpw8VYc8AoEvJ uxf9aBls504l3+/xSPlx5q4= X-Google-Smtp-Source: ABdhPJzCN/BPT06bdlryF/vs4CFSDtodQelsf9lhObRqSOPbOqicG/hwJxnr93HTjJa09SCem247Rw== X-Received: by 2002:aa7:d4c1:: with SMTP id t1mr8218203edr.253.1593414528386; Mon, 29 Jun 2020 00:08:48 -0700 (PDT) Received: from claude.fritz.box ([185.129.54.56]) by smtp.gmail.com with ESMTPSA id 36sm28062931edl.31.2020.06.29.00.08.47 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Jun 2020 00:08:47 -0700 (PDT) Message-ID: <45F22D7E-D8D8-4D36-8AFA-51E661D18454@gmail.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_31B99AF3-4890-420D-AEEB-708044342597" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Date: Mon, 29 Jun 2020 09:08:46 +0200 In-Reply-To: Cc: Andrea Faulds , PHP internals To: "G. P. B." References: <5ef7505d.1c69fb81.a3d3d.67e7SMTPIN_ADDED_MISSING@mx.google.com> X-Mailer: Apple Mail (2.3608.80.23.2.2) Subject: Re: [PHP-DEV][RFC][VOTE] Rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON From: claude.pache@gmail.com (Claude Pache) --Apple-Mail=_31B99AF3-4890-420D-AEEB-708044342597 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > Le 28 juin 2020 =C3=A0 00:53, G. P. B. a = =C3=A9crit : >=20 > My perception is that most of the community finds it baffling why = anyone > would be against this change. >=20 What baffles me, is the amount of discussion around changing the name of = ONE token, whereas it is clear that a bunch of tokens (a few of them = explicitly mentioned during the discussion phase of the RFC) have = incomprehensible names, or worse, misleading names (T_STRING instead of = T_IDENTIFIER), several of them appearing more often in error messages = than T_DOUBLE_COLON (so, to be super-clear, I=E2=80=99m not talking = about T_SL). And at this point I have still restricted my view to the = issue of token name, whereas there is an obvious way to do better at = relatively low cost, namely replacing the token name with a = user-friendly description of the token. I really appreciate the efforts made to make PHP better; thanks for = that. But I friendly suggest that, each time you are going to propose an = improvement, you take first a step back and consider how your change = fits in its wider context. =E2=80=94Claude= --Apple-Mail=_31B99AF3-4890-420D-AEEB-708044342597--