André Medeiros wrote:
Either that, or
ini_set('display_errors', '1');
On 5/15/07, Jim Lucas <[EMAIL PROTECTED]> wrote:
Afan Pasalic wrote:
> hi,
> in php.ini is error_reporting turned off. and, to see an error have to
> open error_log.
> though, for me is much easier to have it on and see the
Either that, or
ini_set('display_errors', '1');
On 5/15/07, Jim Lucas <[EMAIL PROTECTED]> wrote:
Afan Pasalic wrote:
> hi,
> in php.ini is error_reporting turned off. and, to see an error have to
> open error_log.
> though, for me is much easier to have it on and see the errors on the
> screen.
Afan Pasalic wrote:
hi,
in php.ini is error_reporting turned off. and, to see an error have to
open error_log.
though, for me is much easier to have it on and see the errors on the
screen. while developing, of course.
I put on the beginning of the file error_reporting(E_ALL) to "overwrite"
ph
Stut wrote:
Please include the list in replies.
I'm sorry. Clicked on wrong Reply button
:-)
Afan Pasalic wrote:
Stut wrote:
Afan Pasalic wrote:
in php.ini is error_reporting turned off. and, to see an error have
to open error_log.
though, for me is much easier to have it on and see the e
Please include the list in replies.
Afan Pasalic wrote:
Stut wrote:
Afan Pasalic wrote:
in php.ini is error_reporting turned off. and, to see an error have
to open error_log.
though, for me is much easier to have it on and see the errors on the
screen. while developing, of course.
I put on t
Afan Pasalic wrote:
in php.ini is error_reporting turned off. and, to see an error have to
open error_log.
though, for me is much easier to have it on and see the errors on the
screen. while developing, of course.
I put on the beginning of the file error_reporting(E_ALL) to "overwrite"
php.ini
Parse errors are scanned for and displayed before the PHP parser even starts
trying to execute the code itself. I doubt you can usefully intercept them
because anything you may have written into the file to handle them will
never be run.
- Original Message -
From: "Robert Restad" <[EMAIL
Hi,
error_reporting(E_ALL);
BTW: RTFM!
Regards
Michal Dvoracek [EMAIL PROTECTED]
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Thanks Jon.
But, that's for security, right? Maybe even other reasons. I know close to
zero of programming theory, so, why is it bad to have undefined vars on the
code?
--
Julio Nobrega.
Um dia eu chego lá:
http://sourceforge.net/projects/toca
--
PHP General Mailing List (http://www.p
> I develop with error_reporting(E_ALL). It's a major pain to type everytime
>
> if(isset($some_var))
>
> To avoid undefined variable errors. Any tips? If you turn E_ALL on
> error_reporting, what do you do?
Generally I make sure my variables are defined, and if I can't be sure I
use...
if (is
10 matches
Mail list logo
