On Thu, Jun 11, 2020 at 12:14 AM Sara Golemon <poll...@php.net> wrote: > > You know what shows up unambiguously in a google search? "Paamayim > Nekudotayim". > You know what ISN'T unambiguous in a google search? "Double Colon"
Straw man. The point being that you wouldn't have to Google "Double Colon" because it is self explanatory. > Token names shouldn't show up. Everyone is agreeing with that statement. > Universally. Let's fix that problem rather than create new ones by not > addressing the underlying issue. Are you saying that this RFC is creating a new problem? If so, please elaborate. > > Once again I plead for logic and sanity. At least have the courage to put > > it to a vote. > > > > Absolutely. Put it to a vote. I've got my "no" all locked and loaded. Why is this even an RFC? It's not a language change. There seems to be consensus that those tokens should not be exposed in error messages, so changing the name of one is not even a bugfix, it's just an internal maintainability fix ;-) If your position is "if it ain't broke, don't fix it", I think the prudent thing to do would be to abstain from voting. If a change is perceived as positive for at least one person and the rest are indifferent, it's still a net positive change. If your position is "error messages that you have to Google are better than those you don't" then we should be seeing much more RFC proposing to rename things like T_STRING to T_EMAFAI_ONAFAI_SAUKOFE etc. :-D Best regards, Jakob -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
