On 14.08.2014 00:12, James Ward wrote: > I'm not entirely sure that a backwards compatibility break in a minor > release would be considered non-controversial. > > [...] > > I see this as a bad design choice in the language which should be > rectified... just in a major version. >
As it doesn't even work (one is silently ignored) I wouldn't call it a design choice, but a bug or oversight. On the one hand I also agree with Sara that this could've easily been fixed with a commit without RFC. On the other hand I don't think it's an *urgent* fix and there's no pressing need to have it in 5.next instead of next. ~Florian -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
