Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111361 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 28572 invoked from network); 6 Aug 2020 13:35:04 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 6 Aug 2020 13:35:04 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 8C4F71804B4 for ; Thu, 6 Aug 2020 05:33:12 -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-Virus: No X-Envelope-From: Received: from mail-ej1-f47.google.com (mail-ej1-f47.google.com [209.85.218.47]) (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, 6 Aug 2020 05:33:09 -0700 (PDT) Received: by mail-ej1-f47.google.com with SMTP id g19so36292846ejc.9 for ; Thu, 06 Aug 2020 05:33:09 -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=7av7OmQyF0lC9tA4Xt1Mhu12+X/LLbO6OMcpThV7Ae0=; b=c0mWysr4dMCUdgjxZIz9VHVeVZDLcTz6mGdUNEUKI1qONVI4CX/K3JBjGAWPrmNWdo r9Z0AX6C7LUWCBVYIAcsaUHDtjaa1Oo3hT1NNKZIdz8CmincKkfb75AaIsPjqWlZWUM0 HLUsH/s7ye2zXGYYsV6jVBFu8hw0aw7rDJjdoCUuA10l3QmR8k/YbqQWLEvrr42n1OP9 B6kbDODGQs82mYAOY8aSNCzBNbeVRWhspksscZrYrIIqt7LYjwiZOTj2gccKhF7Dp/Nn n+Qr5iMisVp7wbWT/GGiNwvc1w4QbuuWk4MDey2K1tcGRB/CuyBYS/3B+Aa1QVhwPYGC qK4A== 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=7av7OmQyF0lC9tA4Xt1Mhu12+X/LLbO6OMcpThV7Ae0=; b=r4cfUK9PPZSmB0igp4T2rHn2Lp2diPeOMarTIl8EDKCzI5qAo4o8LMJ13sm7KXXype ZmqE+ZOXjw48LE/ENcwfiDfRob/q6tW2t6MOQSEDKQGIl/UOwZeEJfgY/FXbun/ploo1 nfNdhkRkFsX8nTHcq56N3LwlAN71O16mvvXQ70ElaUECpjyHtP59cpIquDc9MW2v4DjB AQg/Q7lwm/LaesBilU8q4Ttbb04f9Hr8CJC+wq4qMuS5Pe0Vax4McqLp37nXW/tnwO/u 5PNcY3ld9EAuqIz9E2Is5NctSY1A4zn1ma4j7VktDN4PMDWeFjvXTfJQSrKQc4UhrVwS /XWA== X-Gm-Message-State: AOAM532GpiMkO8iOo7uVEpZL0yju9XdYG+D5z/GE37H79VItY1kgly9m 9+1TsJ92+QzRQR/1RNTt9q8= X-Google-Smtp-Source: ABdhPJzAM+kI7rP0bvrO6qZ06mqLMSYHq5gt3cKYfuYu3RA/CClnM5s9tOfu2LNUhO30M6DVLK3fQA== X-Received: by 2002:a17:906:7f0b:: with SMTP id d11mr4438973ejr.116.1596717185452; Thu, 06 Aug 2020 05:33:05 -0700 (PDT) Received: from claude.fritz.box ([89.249.45.14]) by smtp.gmail.com with ESMTPSA id u24sm3372745edq.23.2020.08.06.05.33.04 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Aug 2020 05:33:04 -0700 (PDT) Message-ID: <573869A2-CCD0-49CC-9953-E42257B6862D@gmail.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_065FDCBF-0CFC-4BFF-AD30-BD91C681FC04" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\)) Date: Thu, 6 Aug 2020 14:33:03 +0200 In-Reply-To: Cc: =?utf-8?Q?C=C3=B4me_Chilliet?= , PHP Internals List To: Benas IML References: <20200806091749.64675445@mcmic-probook.opensides.be> X-Mailer: Apple Mail (2.3608.120.23.2.1) Subject: Re: [PHP-DEV] [RFC] Shorter Attribute Syntax Change RFC 0.2 From: claude.pache@gmail.com (Claude Pache) --Apple-Mail=_065FDCBF-0CFC-4BFF-AD30-BD91C681FC04 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > Le 6 ao=C3=BBt 2020 =C3=A0 10:11, Benas IML = a =C3=A9crit : >=20 > Ending delimiter MAY help us in the future. >=20 > I really, really hate all of those arguments stating "that we should = care > only about the present, not the future" and that even though > `#[...]`/`@[...]` might bring benefits in the future, we should still > choose `@@`". >=20 > This shows clearly that some people are basing their views on = subjective > reasons rather than being objective. >=20 > As far as this discussion is going, I see pro-`@@` people just saying > "Arghhh, let's keep @@, it doesn't bring any benefits that other = syntaxes > do but we don't need them anyways, let's not speculate future". >=20 > It's like saying you can either go through door A and get a free car = or > through door B and get the same car and **maybe**, even an additional > 1,000$. >=20 > We are playing probabilities here but at the moment, no one has said = any > substantial argument why `@@` is better and thus, `@[...]` seems like = a > better option in the long term. >=20 Note that, in a hypothetical future where the absence of delimiters = would lead to (perceive or real) ambiguity, it will always possible to = add optional ones, as in: `@@simple("thing")` and `@@{very("complex") = thing}`. =E2=80=94Claude= --Apple-Mail=_065FDCBF-0CFC-4BFF-AD30-BD91C681FC04--