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
