Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111536
MIME-Version: 1.0
References: <alpine.DEB.2.23.453.2008100935570.7489@singlemalt.home.derickrethans.nl>
 <BYAPR05MB65355FFBB6717491995EEBF4DE420@BYAPR05MB6535.namprd05.prod.outlook.com>
 <CAESVnVqraG9V4VMrxrv5AOFX5Jt7Cx0-uo5L0doQEWcUVOdHkg@mail.gmail.com>
 <BYAPR05MB65356FCC029CD06F49F528A0DE420@BYAPR05MB6535.namprd05.prod.outlook.com>
 <CABdc3WobP1HSRwcujd4=o4wv3QUp7gDT12KmMRQU1_wLj4YLuQ@mail.gmail.com>
 <BYAPR05MB65351C807797676BB08D8BDCDE430@BYAPR05MB6535.namprd05.prod.outlook.com>
 <5cc837df-ab47-628a-d29b-46d7933be973@gmx.net> <BYAPR05MB653522F9123B59F7E066BDB8DE430@BYAPR05MB6535.namprd05.prod.outlook.com>
 <3A7CECC3-CDEE-4852-BF4B-4EC7CA1BD538@pmjones.io> <CAAKU0u=VYh7D+XJ93dDdAxdJ8nEU8iPfeN0f=Xv9Qm=cCQKX6w@mail.gmail.com>
 <BN8PR05MB6532D19BEA11F44BAAD3FDD3DE400@BN8PR05MB6532.namprd05.prod.outlook.com>
 <CAESVnVp5NHKKpMHt_7AAO8P9L2vL8UN4ynD5K4d9f23Jvr+s2A@mail.gmail.com>
 <alpine.DEB.2.23.453.2008141902160.7489@singlemalt.home.derickrethans.nl> <65503c70-e0f0-19b0-0e9e-8b1321510a46@telia.com>
In-Reply-To: <65503c70-e0f0-19b0-0e9e-8b1321510a46@telia.com>
Date: Sat, 15 Aug 2020 15:00:32 +0300
Message-ID: <CANeKSiR_Rv80N2E-PARuYR-+ct+cV97YE0To-htJZ7aMPSC22g@mail.gmail.com>
To: =?UTF-8?Q?Bj=C3=B6rn_Larsson?= <bjorn.x.larsson@telia.com>
Cc: Derick Rethans <derick@php.net>, Sara Golemon <pollita@php.net>, 
	Theodore Brown <theodorejb@outlook.com>, Benjamin Eberlei <kontakt@beberlei.de>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000008d5ab905ace94962"
Subject: Re: [PHP-DEV] [VOTE] Shorter Attribute Syntax Change
From: benas.molis.iml@gmail.com (Benas IML)

--0000000000008d5ab905ace94962
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Aug 15, 2020, 2:53 PM Bj=C3=B6rn Larsson <bjorn.x.larsson@telia.com=
>
wrote:

> Den 2020-08-14 kl. 21:23, skrev Derick Rethans:
>
> > On Fri, 14 Aug 2020, Sara Golemon wrote:
> >
> >> Derick was trying to be good and meet my beta3 deadline.
> > And I even got that date wrong by a week. Oops.
> >
> >> Fortunately, I gave him that deadline (while thinking RC1) knowing
> >> some kind of bullshit like this would come up and LO AND BEHOLD here
> >> we are.  So the good news is that we actually have a spare two weeks.
> >> On Fri, Aug 14, 2020 at 7:22 AM Theodore Brown <theodorejb@outlook.com=
>
> >> wrote:
> >>> 2. Include a ranked voting option for @: and mention its pros and
> >>> cons (it is equally concise as @@ with no BC break, but is somewhat
> >>> harder to type). Patch link:
> >>> https://github.com/theodorejb/php-src/pull/1
> >> Glancing at beberlei's reply, I do agree that @: is coming slightly
> >> out of left field.  However, we're using a STV system, so might as
> >> well go wild with the options (within reason).  HOWEVER, any option
> >> included is going to need the same care applied as you outline in #3
> >> and #4 below.
> > I would like to point out that as the main premise of the RFC was that
> > the chosen syntax had no ending delimiter, I would say that any new
> > suggested syntax should have one before I would be willing to consider
> > adding it.
>
> I think that lack of ending delimiter is not a good enough reason to
> exclude the @: syntax from the RFC and voting. Would be good to
> have the community view on this in order to put this to rest!
>

No, the community view does not matter here. Including `@:` would go
against the core values that this RFC is proposing: an attribute syntax
that has an ending delimiter.


> We have the @@ syntax in the voting and of course that's natural.
>

We have it in the voting poll since it's our current syntax; there are no
other reasons.

Still adding the @: option would in my eyes give a more complete
> view of feasible syntax choices. The far fetched ones should not
> be included of course.
>

Which would go against the entire premise of this RFC. If someone wants
`@:`, he/she should create separate RFC.


> r//Bj=C3=B6rn L
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>

--0000000000008d5ab905ace94962--