On 27/10/2013 15:51, Nikita Popov wrote:
Unless we have *concrete* plans regarding PHP 6 saying "this should go into (a hypothetical, non-existing) PHP 6" is roughly equivalent to just declining the feature.
I agree with that, and think it is a real problem, but there are two solutions: abandon the BC rules for 5.x releases, or make some concrete plans for 6.x.
Otherwise, the release process might as well not distinguish minor and major releases at all, and just define what is and isn't allowed in terms of BC for the foreseeable future of PHP.
PHP 6 only makes sense to me if we're planning to actually do changes with major BC impact. Not things like this RFC, but changes of basic language semantics (like fixing the 0 == "foo" comparison and other foundational issues).
Not every major release has to fix everything. An overhaul of error handling, in general, would seem like a good Big Feature to pin a major release on, just as Unicode strings would have been, had it gone ahead.
-- Rowan Collins [IMSoP] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
