Derick Rethans wrote:
If you decide not to fix the 4.x branch then we'd minimally need an easily
accessible document describing the known problems and work-arounds IMHO.
As I tried to do that in our large code base, I would say that's totally
not possible to do. There is no way you know you're doing someting
wrong, as there are no warnings and go through 200k+ lines of code
without missing an instance is impossible.
That's a misunderstanding then. I was meaning work-arounds on the user
side like avoiding certain constructs.
But I'll leave it to the PHP gods to figure out how to continue :-)
- Chris
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
