Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111601 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 42903 invoked from network); 17 Aug 2020 23:10:25 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 17 Aug 2020 23:10:25 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D452918050B for ; Mon, 17 Aug 2020 15:11:25 -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-lj1-f172.google.com (mail-lj1-f172.google.com [209.85.208.172]) (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, 17 Aug 2020 15:11:25 -0700 (PDT) Received: by mail-lj1-f172.google.com with SMTP id g6so19158047ljn.11 for ; Mon, 17 Aug 2020 15:11:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=c0Frb5gcLWIfqjP3MwG3Bgk08qEYa5C14X+jY0uoxGQ=; b=LWOmXbIiP1HABD2Amhc4lqeGu6lFskX1cIPXPGNkf5OWxn/u0IE7UVXVqfRX5QNrKK 0l073sS8e/lM/roCVnoaMRpqbtHZuGYGk721RasW3zUO+TIEgFxqLlF5KjKq6m95kG2c zLSFiYTGC8TcdzRmC48hfcLsuKYIUiJMbl3Fg3tnjk/LrmZtblxigCSSIgbJSOxOtsJu rOHvRZNbXRKBTzWHk+bD4+XmEnKqD6bR72XzPgzItIoAus1AFzuIr+hQYCFtQ7oC0rB7 X2qMELCAyBXDoArak7Ihz4sJIMDEGPsC2/fXU3P2ZtX4l/qeN7Li9gbsfAu2voa6BwtZ POWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=c0Frb5gcLWIfqjP3MwG3Bgk08qEYa5C14X+jY0uoxGQ=; b=HdL0nYUhrDTLaBReIdQZch/dEoD7sNKK0RHBy0iron9gjfP3TWZbMU+Q68PfW+svhl PbVgdvYudGreU85FbwvrxKC3ximD+fkFEEGD9T97pFu2zpYGG8VnutITX/HC1GpsysW8 TGQjW8MJJKyPfI3Y/M/dSxE3YpwNtbVRs8gVT/t1Jh+XUzAk6zUHGXzzvsoAl4S/Sad9 hs59haM6Uc23sxLBUUQFxaLDumJFw4oNRhj1XGI5WYCIN+1hSVK11QJSddxP/0wNlM3J XOT7COhw661cuMn2h9fda0kNZWNHywHDd3exIHAhYtHw8t1uv5TtHtjoTizIuI/fr7b6 P0EQ== X-Gm-Message-State: AOAM530nb+hP288IBsiVxLH37JkjuPLJ6hQyMINZWk/q4NqfGrajFwTY oL9ujEkmSB+ANwUFlIWPb2QYEfKKL7sSLN4ChKk= X-Google-Smtp-Source: ABdhPJxFj7f3IrHNEu/eivLAG53ennIRhHkLRYFEtShQWZOiprSze/m7Ev8k95VqGrcTrDQEiUw0oIgaJi8jlPuUSSU= X-Received: by 2002:a2e:1417:: with SMTP id u23mr8875226ljd.44.1597702283002; Mon, 17 Aug 2020 15:11:23 -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: Tue, 18 Aug 2020 01:11:10 +0300 Message-ID: To: Jakob Givoni Cc: Benjamin Eberlei , Benjamin Morel , =?UTF-8?B?TWljaGFlbCBWb8WZw63FoWVrIC0gxIxWVVQgRkVM?= , PHP Internals Content-Type: multipart/alternative; boundary="00000000000009073c05ad1a0d3a" Subject: Re: [PHP-DEV] [VOTE] Shorter Attribute Syntax Change From: benas.molis.iml@gmail.com (Benas IML) --00000000000009073c05ad1a0d3a Content-Type: text/plain; charset="UTF-8" On Tue, Aug 18, 2020, 1:04 AM Jakob Givoni wrote: > Hi Benas, > > On Mon, Aug 17, 2020 at 11:34 PM Benas IML > wrote: > > > > On Tue, Aug 18, 2020, 12:25 AM Jakob Givoni wrote: > >> > >> The question is now if it's reasonable at all to change something for > >> 99% purely subjective reasons (no other substantial fact has been put > >> forward other than the VIM argument) well past feature freeze (yes I > > > > > > In the future, syntax with an ending delimiter might help us to not run > into new parsing issues like `@@` did. > > > > And yes, the future DOES indeed matter. I hate when people who don't > contribute to or maintain the php-src actively try to tell otherwise. > > I sincerely hope you're not trying to put words in my mouth. Don't be a > d*ck. > I was not referring to you specifically. But if you re-read these past 2 week discussion, most of the people being ignorant on the idea of "future parsing issues" are people, who aren't maintaining PHP. > > Again, in the future we might introduce a new feature that might make > > attributes have more complex parts than just an argument list. In this > > case, `@@` or `@:` is only going to f*** us up. > > It sounds like you want to develop a whole new language inside those > attribute blocks... Not sure that's a good idea either, because, you > No but we won't be able to implement a single new feature to attributes (besides nested attributes) since anything more complicated (e. g Benjamin's example) requires an ending delimiter. know, as they say, the future DOES indeed matter ;-) > > Regards, > Jakob > --00000000000009073c05ad1a0d3a--