+1 The merits of E_STRICT shouldn't be ignored for development. That being said, it isn't suitable for a production environment.
Additionally, it should be a user-facing option (stored in the DB) to set the error level. Ideally we would have different levels possible (development, production, etc.) On Nov 24, 2008, at 10:38 AM, Rich Bowen wrote: > > > On Nov 24, 2008, at 01:50, Stenehall wrote: > >> >> Could a solution be a checkbox in the admin-panel, "enable more >> extensive error reporting"? > > +1 > > I think my earlier message got lost in the ether while our network was > down. > > I'm a huge advocate of E_STRICT in development, but since we have no > control over what third-party plugins will be installed, it is not > sensible to have E_STRICT enabled in our released production build. > > -- > "There are two kinds of light--the glow that illuminates, and the > glare that obscures." > James Thurber > > > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
