> On Tue, 20 Aug 2002, Andi Gutmans wrote: >> I still think it shouldn't go in. This is the only feature in Engine 2 >> which might make non-OOP people convert. Once this isn't in Engine 2 we >> don't have a carrot for them.
[..] > I'm +1 for getting this backtrace thing in PHP asap. It's more > useful for my work than any of that OOP stuff ZE2 has. And I'd > rather have it now than wait indefinately for PHP 5 to be released. > > --Jani If the code wont be committed to the main PHP 4.x download, can a patch be provided for those of us gagging for backtracing in our php development. The amount of time it would save me is phenomninal. Today I found a bug in my 5 meg (accumulative) scripts, all of which use a $mysql->query() method. The error shows up as being thrown in the query, but I have no idea out of the tens of thousands of lines of code which called it. A backtrace in this case would be like gold dust. Could we not just release a patch to the people that want it (well, need it!), and leave the "official implementation" until PHP5? That way the carrot remains, but nothing is held back from the people who desperatly want it. -- Dan Hardiker [[EMAIL PROTECTED]] ADAM Software & Systems Engineer First Creative Ltd -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
