I agree with you that the parameters would be good. There should also be the
limit parameter (same as for debug_backtrace). However I'm afraid I'm not that
much familiar with C to actually write it.
It's true that in 'args' there theoretically may not be any object. But as you
are surely aware, the probability of that is pretty much zero in a real PHP
application. Unless it does not use OOP of course, but in that case the
'object' field would also be empty.
That means it would be good to add the parameters to Exception::getTrace(), but
as I'm unable to do so there won't be anything wrong with just adding the
'object' for the timebeeing, don't you think? It would be very helpful for
those who use some fancy debugger (see
http://blog.juzna.cz/2011/07/tuning-error-reporting-in-php/).
Dne Sun, 06 Jan 2013 00:50:22 +0100 Stas Malyshev <smalys...@sugarcrm.com>
napsal(a):
Hi!
I don't understand. There already IS the 'args' field where huge
objects also can be (and very often are). The new 'object' field
does not make any difference in this regard.
It adds another place where huge objects can be - and unlike args, it is
guaranteed to be an object, and those tend to be big. So chances to blow
up the memory with this function become higher. That's why other
functions gained parameters to amend this situation some time ago, this
one would be good to add it too.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
