Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111576 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 44442 invoked from network); 17 Aug 2020 13:22:24 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 17 Aug 2020 13:22:24 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id C19301804C2 for ; Mon, 17 Aug 2020 05:23:18 -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=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-wr1-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) (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 05:23:18 -0700 (PDT) Received: by mail-wr1-f42.google.com with SMTP id r15so4858941wrp.13 for ; Mon, 17 Aug 2020 05:23:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=beberlei-de.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ODKsA2fkQB0qjgwrjptEwmTgdJeiJvTCaFGwBQmgD2Q=; b=JPI0PipLYdAl7CQSwhWV61BfGJFh86StsA4h+9mo6xnbrtST3MVJBtmGHqlL+9zNQm iru2s7rMQdNtz7FwSY5rAZP4ZSrWQB4tG0YZzZx5HmXsRblCekgk6K3/aFLtFzmVZU2r hFQYFKdPNDCrmGVwj36mLG+oc0G+E132bZb/rnK79EDLwmylXMLK3z/5gLVBAdjD6/2l 2oVjXoJPQCG7Cv1rq6CDC0xv1jVUGhobk6uQj9h9fHsDr3Gv1X3Lfq0fT8B29tAsXHAR Dm0UWXm2cgurltxWoxAOhGVLF1/hRpXWz42adFby34vEjJdn99InrxSOxTFC12+3G6R/ GZOA== 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=ODKsA2fkQB0qjgwrjptEwmTgdJeiJvTCaFGwBQmgD2Q=; b=fWys9/9ia2im4CFa9c0Ka8iDxchLui26oxYqea6oXcqBexKzQWeKiN6okSOpX0ZIsu rXQpgE6jvjlbw90WKP/zIb4xMFBPOGgw6DEqPJGR8XzTdgEM/rW3FAd9ZA89+boTTq+F 4oXdl1bok1pdsfs6GocwfCNKp/QPmTqC1wMWvU+p270fRhOoBwivAU+d+wUNsNM8PJs7 7ZZ8Wl681gCPjXGsEQjF/Ln37GlFKz4eUkX2EKL2jU4RUIOB3+M1CBxxWI72FBiBnucO fXuCZWD4qNThzTKhm5a6dIppwq1d/lANnlPqFPeC23hT6nRCM6nhwpQ1aY5qv3+aL/hP a4rQ== X-Gm-Message-State: AOAM532yw/4H6xFFIbisttWc35VIZXksx5DWsiOcVT9gKTtu0YyjVqLx nZ1b7cwg2FGPJ2U9LYPVotmue/DAZmTV/+odaXXZhw== X-Google-Smtp-Source: ABdhPJyh01L/1I5vNQU/DuQR6DtDWRnuNf69Ih4bAD35f6/QlhvsvMmN1l7AZjDL56Cl+EqDGPCsWkCbz3ZZOoGlqhE= X-Received: by 2002:adf:dcc8:: with SMTP id x8mr15993803wrm.16.1597666996549; Mon, 17 Aug 2020 05:23:16 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 17 Aug 2020 14:23:05 +0200 Message-ID: To: =?UTF-8?Q?Alexandru_P=C4=83tr=C4=83nescu?= Cc: Derick Rethans , PHP Developers Mailing List Content-Type: multipart/alternative; boundary="000000000000cc91c705ad11d527" Subject: Re: [PHP-DEV] [RFC] Shorter Attribute Syntax Change RFC 0.2 From: kontakt@beberlei.de (Benjamin Eberlei) --000000000000cc91c705ad11d527 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Aug 17, 2020 at 10:59 AM Alexandru P=C4=83tr=C4=83nescu wrote: > On Sun, Aug 16, 2020 at 12:36 PM Benjamin Eberlei > wrote: > > > > We have updated the RFC with all (hopefully) of the feedback from this > > discussion: > > > > https://wiki.php.net/rfc/shorter_attribute_syntax_change > > > > Most notable changes are: > > - A new section with several subsections on the benefits of a closing > > delimiter / enclosing syntax. > > - A section on grouping pro/cons > > - Inclusion of @: as per Theodores request > > > > We are looking for further feedback from the community. > > Thanks for the work. Looks good. > An idea. > > Would the syntax @ be able to obtain a "No" on the "Breaks BC of > valid PHP 7 code" section while still being more or less the same as > #[Attr] or @[Attr] considering other features? > BTW, I'm thinking that it's good to have a "No" there. > > Sorry if proposing another syntax is making this an even more complex > problem. > It is ok to propose another syntax, at this point in time we are working around the @ and [] symbols, because of their familiarity with other languages attribute syntax. There is probably 100 potential syntaxes that we could use, @<> is a bit hard on the eyes as is <<>>, so i wouldn't call it a game changer in contrast to what we have already, so I would rather not include it. > > Regards, > Alex > > > On Tue, Aug 4, 2020 at 3:46 PM Derick Rethans wrote: > > > > > Hi, > > > > > > Out of Banjamin's suggestion[1], I've updated the Shorter Attribute > > > Syntax Change RFC to reflect that process: > > > > > > https://wiki.php.net/rfc/shorter_attribute_syntax_change > > > > > > Patches and comments welcome. > > > > > > FWIW, this has an excemption from the RM Sara as per [2]: > > > > > > > * Shorter Attribute Syntax Change > > > > - Joe/Derick - Please make sure this RFC moves along and reaches > > > > conclusion by beta3, as discussed previously. > > > > > > > > > cheers, > > > Derick > > > > > > [1] https://externals.io/message/111218#111261 > > > [2] https://externals.io/message/111286#111286 > > > > > > -- > > > PHP 7.4 Release Manager > > > Host of PHP Internals News: https://phpinternals.news > > > Like Xdebug? Consider supporting me: https://xdebug.org/support > > > https://derickrethans.nl | https://xdebug.org | https://dram.io > > > twitter: @derickr and @xdebug > > > > > > -- > > > PHP Internals - PHP Runtime Development Mailing List > > > To unsubscribe, visit: https://www.php.net/unsub.php > > > > > > > --000000000000cc91c705ad11d527--