Hi,
Tom Worster wrote:
I agree with Sara all the way except the opinion that it's too late to
fix this bug with option B, which I think is the right one.
I simply don't know if it is too late or not so I suggest Peter enter a
bug report and see what happens. If it's too late for 7.0.0 do it in
.0.1, which is ok because people will expect instability with 7.0.0.
\u{394}semver > 1 is sufficient warning, I think.
The RFC was passed with 92% voting in favour, and that RFC INCLUDED the
error behaviour explicitly.
If people really want to butcher it under the guise of "consistency" and
cause future pain when the Unicode consortium does something weird, we
should have yet another discussion and voting period. We shouldn't just
"fix" it quickly because three people on the mailing list think so.
Thanks.
--
Andrea Faulds
http://ajf.me/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
