Hi! > Better error messages are obviously better than just replacing the name of > the token, however this argument is saying that because this isn't perfect > let's do nothing.
I don't think this is the argument. I think the argument is rather than half-fix the problem wrong way, let's fully fix it the right way. > I find it highly frustrating, and borderline offensive, that we are being > asked to go from a simple, non BC breaking, easy to enact change, to a > semi-major overhaul of how error messages should look like. I personally I am not sure why is this "offensive" to you. Is there something in overhauling error messages that goes against your principles or religious beliefs? Sometimes overhauling is exactly what is the right way to go, and not showing internal parser tokens seems to be quite reasonable idea. If this idea is somehow "offensive" to you, I feel sorry for you but it's not a reason to abandon this idea. It is also quite a common things - many proposals in PHP have been rejected because the community thought it's not the right way to approach things, I myself have had some proposals rejected because of this. There's no reason to feel offended by that. > My perception is that most of the community finds it baffling why anyone > would be against this change. My perception is that most of the community couldn't care less for how the tokens are named, and really shouldn't. It's an internal thing and should stay this way. If they made to care, that's our fault and we should fix it. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
