Re: E_NOTICE

Quoting "Stig S. Bakken" <ssb@alltheweb.com>: > With the recent security discussion on php-dev in mind, I think we > should start to develop our PEAR code with E_NOTICE enabled. It's a > real pain in the ass in the beginning, but chances are you'll find bugs, > and people who switch to "more annoying" error reporting as a result of > this discussion or changed defaults in coming PHP versions will be able > to start using your code without @-silencing every single call. I've been writing all of my php code with error_reporting(E_ALL) on for three years now. It's not a pain in the ass, it's just good programming practice. And it really does point out a lot of things that might not be obvious at first. I think it would be _very_ reasonable to require all PEAR code to run cleanly at the E_ALL level. -chuck -- Charles Hagenbuch, <chuck@horde.org> Some fallen angels have their good reasons.