> On Feb 19, 2020, at 12:27 PM, G. P. B. <george.bany...@gmail.com> wrote: > > But that's Golang's policy,
The intent was not to present someone else's policy but to instead show prior art. > so either we change all error messages to be lower case or we keep it > consistent with what PHP currently does. > Moreover, I'm not sure I see a massive benefit in having it in lowercase > (especially just one random function which behaves not like others) That is certainly one position to take. Another position is to evolve and adopt newer practices rather than be fixed by to choices made in the past that do not address concerns that have been identified since the original choices were made. And with that, that is all I will say on this topic. Take the outcome where you will. -Mike -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
