|
|
Posted by Kimmo Laine on 12/28/05 11:42
"Erwin Moller"
<since_humans_read_this_I_am_spammed_too_much@spamyourself.com> wrote in
message news:43b257d7$0$11077$e4fe514c@news.xs4all.nl...
> Michael wrote:
>
>> Erwin,
>>
>> Thank you for taking the time to respond with your clear and helpful
>> response. Used ini_set, and it works fine. Much better than looking at
>> the error log.
>
> Good. :-)
>
>>
>> By the way, do you happen to know if there are any useful PHP
>> IDE/Debuggers out there? ... the type of environment where you can
>> single step, set breakpoints, inspect variables, etc.?
>>
>
> Yes, just google for them.
> I have no advise because I never needed them. As in Never.
> And I make my living as PHP developer. :-)
>
> Two things that are extremely helpfull when debugging/coding:
> 1) Errorreporting on (for all errors and notices and warnings)
> That one you have up and running already. :-)
> 2) Just output your variables to the html.
> An extremely usefull function for this is print_r($somevariable)
> If you have arrays, no matter how complex, the follwing example will
> format
> them for you:
> from html:
> <pre>
> <? print_r($myComplexArray); ?>
> </pre>
>
> If you want to print an object, you can also use print_r().
3) Use debug_print_backtrace();. It really helps if you're dealing with
included files, to show where the function or method call really originated.
--
"En ole paha ihminen, mutta omenat ovat elinkeinoni." -Perttu Sirviφ
antaatulla.sikanautaa@gmail.com.NOSPAM.invalid
Navigation:
[Reply to this message]
|