OMG the trolling continues even today with this nonsense. Disappointing. Calling T_PAAMAYIM_NEKUDOTAYIM a non-issue is simply wrong and here's why:: "People don’t ask for the other parse errors even half as often as they as for T_PAAMAYIM_NEKUDOTAYIM They do so because it looks like gibberish to them, so it looks unlikely to be a common thing you can Google, nor it gives something recognizable to start with [sic] Yes, we all acknowledge it’s an easter egg joke that refers to the creators of PHP. But that particular joke has outworn its welcome in the community after repeatedly CAUSING SUPPORT ISSUES." -Stan Vass (emphasis mine)
"It's a minor change and an annoyance to a lot of people. Yes, by not changing this you’re annoying thousands of people." -Alexander Schrijver "It’s the same argument everyone else is giving, and really it all comes down to this.: Nostalgia is valued over clarity and consistency. Do you guys REALLY want to claim that?" -Chad Minick "...yes, it is broken, people have to Google or ask around for a very unclear error message when for the most part errors are (and should be) self explanatory ...Two things are broken: Either the token is named badly, or the token names shouldn’t show up in error messages at all and be replaced with something a bit more friendly. ...What is so hard to believe when people see UNEXPECTED T_DOUBLE_COLON on LINE 23 they are gonna look for a double colon on line 23?" -Chad Minick Once again I plead for logic and sanity. At least have the courage to put it to a vote. On Wed, Jun 10, 2020, 12:28 PM Claude Pache <claude.pa...@gmail.com> wrote: > Hi, > > I appreciate the effort to reduce frustration in PHP coding. > > However, T_PAAMAYIM_NEKUDOTAYIM is a non-issue: you learn it once and > you’re done for the rest of your life. > > May I suggest an improvement that would be much more useful than renaming > tokens? > > One parsing error that I still find dreadful after more than 10 years of > PHP coding, is: unexpected T_CONSTANT_ENCAPSED_STRING. Although > T_CONSTANT_ENCAPSED_STRING is like Hebrew for me, I’ve learned with time > that when I get such an error, it means that I’ve most probably omitted or > mistyped some punctuation mark somewhere. However, PHP is unable to tell me > where exactly is the error: it tells only the line number, and I have to > carefully scan the entirely line to find the place. Sometimes, I resort to > split the offending line in several ones, so that I could get more precise > location info. > > So please, let the parser tell me not only the line of the error, but also > the column. Then, it doesn’t matter how the offending token is named if you > know where it is. > > —Claude > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
