Hey,
I think we need to clearly differentiate between features/limitations and
bugs. Often people on this list think that the former, especially
limitations, is something which desperately needs addressing, whereas I
think that addressing such issues in only the latest versions is fine (and
sometimes it's even better to live with it then over-design the language).
Now as far as bugs are concerned, we will never be able to resolve all
bugs, but we should try and solve the ones which can seriously bite people
especially if they are hard to detect *and* it's not clear how to work
around them.
I think in this case, the bug we are talking about falls into the category
of hard to detect and hard to work around. Therefore, I *do* think we
should release a new version of PHP 4 which resolves this bug, and I think
we should stick to the rule and not break binary compatibility, thus having
a 4.4.x version. If there are other bugs which can be addressed for 4.4.x
that's nice but don't make it the holy grail or it will never be released
(email to follow regarding 5.1 tomorrow).
Again, I think the fact that this bug has appeared a few times, has caused
a lot of pain, and is hard to understand and work around, it'd be best to
address it.
Andi
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
