I can see your point. The new object-oriented Zend_Log design is great for application-level logging, because one would configure a log object and use it throughout the app. But debug-printing is ad hoc. It needs to be quick to write the code, much more than it needs to be object-oriented.
I don't mind it being Zend_Debug::dump(), but I don't want people to believe that the Debug class will contain methods to set breakpoints, monitor variables, perform traces, generate code profiling reports, or sniff TCP/IP packets. Those kinds of advanced debugging features need engine support, a real debugging tool, and perhaps external tools. Those solutions are already available and it would be foolish to duplicate them in the Zend Framework project. So as long as everyone understands that a Zend_Debug class contains only userland functions like dump(), I have no objection. Do you have another suggestion that is consistent with the goal of eliminating Zend.php from the library? Regards, Bill Karwin > -----Original Message----- > From: Stanislav Malyshev [mailto:[EMAIL PROTECTED] > > I really don't think that's a good replacement for Zend::dump.
