On Tue, Aug 18, 2020, 1:04 AM Jakob Givoni <ja...@givoni.dk> wrote: > Hi Benas, > > On Mon, Aug 17, 2020 at 11:34 PM Benas IML <benas.molis....@gmail.com> > wrote: > > > > On Tue, Aug 18, 2020, 12:25 AM Jakob Givoni <ja...@givoni.dk> 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 >
