Re: consider reverting E_ALL with E_STRICT
Am 07.03.2012 01:11, schrieb Alan Knowles:
> Sorry - top post as I can't reply to all the mails on the thread..
>
> - display errors on.
> Yes, this is a business decision, 20 servers running upgraded at different times, some have
> less maintenance others
> have more.. Seriously, the chance of me even bothering to check one of those log files is
> pretty slim. However if
> the code is producing warning/notices etc. then that is likely hiding a unexpected behavior
> that the client will
> report as a bug anyway later, so it's proved over many years to be cost effective to have
> them display, clients
> report problems, and we can fix them.. They kind of like that service....
it takes 10 minutes to write a script running hourly or whatever
you want per cron, mailig you the error-log and reset it at the
same time
what you are doing is gambling that a random user will notify
you about warnings not realizing that they mostly not do
NEVER rely on a enduser reporting problems where this can
be automated especially because php-warnings in the source
code often breaks applications by have them in a form-value
or in javascript parts, having them in a from-value can
easily result in post them finally in a database
this is not a business decision, this is poor administration
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Thread (14 messages)