Reading php.net's example of setting display_errors
with ini_set
:
<?php
echo ini_get('display_errors');
if (!ini_get('display_errors')) {
ini_set('display_errors', '1');
}
echo ini_get('display_errors');
?>
Is there a good reason as to why we're checking to see if display_errors
is false before we set it to true? Surely it would be faster to not bother checking and just set it to true if that was our intention?
I would be really appreciative if someone could enlighten me on this; as should I be doing something similar with error_reporting(-1);
too?
Thank you all!
Is there a good reason as to why we're checking to see if display_errors is false before we set it to true?
It's an example. No, there is no deeper reason. Overriding "true" with "true" also is valid.
Surely it would be faster to no bother checking and just set it to true if that was our intention?
I guess you would rarely feel any difference, wether you check it first, or not.
However: You should use php.ini
for this and more important: Never enable display_errors
on a live system!