Marco Tabini schrieb:
> A two-liner is twice as many lines as a one-liner :-) .
Thats why I pointed to auto_prepend_file.
> In a debugging
> situation, you often add and remove var_dump()'s quickly and all over
> the place while hunting down a bug. Having to worry about an extra step
> uselessly complicates things, in my view.
Yes. But that's only one way of debugging.
> If using the built-in functions is not any more complicated than using
> PEAR, then why not get rid of them at all? Because they are useful, of
> course. Except that in their current form they are less useful than they
> could be.
Right. var_dump in HTML is a pain. But IMO PHP should provide only a
core of functions. Functions for the basic use of the *language*.
You can put anything into PHP itself, but this makes PHP bigger and
fatter.
$ ls -l `which php` | awk '{ print $5; }'
4009419
(That's the biggest binary on my machine, btw.)
Yes, your patch adds only a few lines ...
>> Using Var_Dump makes your script slower, but (high-)speed doesn't matter
>> while debugging PHP scripts.
> Agreed. But high development speed does matter, and having to use PEAR
> doesn't help you there.
PHP is not (yet?) designed to do good PHP script debugging.
> In any case, the discussion is sort of moot, since the patch won't be
> applied.
I'm just a user of PHP, I don't have to decide that.
> I'll just use it for my internal purposes, and it's in the
> archives for anyone who may find it useful.
There is also a PECL package for debugging purposes:
http://pear.php.net/package-info.php?pacid=214
Frank
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
