Posted by W Marsh on 07/15/07 17:19

On 15 Jul, 18:04, ZeldorBlat <zeldorb...@gmail.com> wrote:
> On Jul 15, 10:52 am, W Marsh <wayne.ma...@gmail.com> wrote:
>
>
>
> > Yuck. I dislike PHP, as a language. I wish that I didn't have to use
> > it. It seems almost designed to catch the programmer out - a syntax
> > error should be rigid. The fact that the code works anyway seems more
> > like a "syntax recommendation". It is ridiculous for PHP to make the
> > assumption that the programmer has read every detail of the (poor)
> > documentation that exists for language elements, and punish the time-
> > pressed newcomer by expecting him to know that there is an option for
> > enabling all errors.
>
> That's because you, like a lot of other people who have problems but
> can't figure out why, have error_reporting turned off. In a
> development environment it should be set to E_ALL with
> display_errors() turned on. In a production environment it should be
> set to E_ALL with display_errors() turned off and log_errors() turned
> on.
>
> Way to many people don't see such problems because error reporting is
> disabled. The problem is further compounded by the people who suggest
> that you can "fix" the issue of notices and warnings appearing by
> simply disabling it. Just because you can't see it doesn't mean it
> isn't there.

Re-read what I wrote:

"It is ridiculous for PHP to make the assumption that the programmer
has read every detail of the (poor)documentation that exists for
language elements, and *punish the time-pressed newcomer by expecting
him to know that there is an option for enabling all errors.*"

[Back to original message]