At 17:40 30/05/2005, Christian Schneider wrote:
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.
Yes, that's what Derick and I are talking about too. What Derick is saying
is that finding the problematic pieces of code can be a long, agonizing
process. Then again, a lot of bugs fall in the same category...
Zeev
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
