Derick, Thank you! Thank you! Thank you!
The problems with references are one of the main reasons I watch this list. As others have stated, with many tens of thousands of lines of code, it is extremely painful to figure out which misplaced or missing "&" has caused php to lose its mind. The fact that php loses its mind in these cases has left me with the impression that php is sort of a second class language. Putting the reference bugs to rest are the most important bug fixes I can imagine. (No, I don't think it will be feasible for us to move to php 5 anytime soon.) Thank you! - Todd Ruth On Mon, 2005-05-30 at 16:44 +0200, Derick Rethans wrote: > On Mon, 30 May 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. > > That's what I meant too. "Our large code base" is a PHP application. > > Derick > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
