I'm all for simplicity, I just thought it could be useful to have multiple deprecation error types. If others agree that simply throwing an E_USER_NOTICE error is enough, we may well archive the proposal.
Best regards, Tobias 2008/7/17 Bill Karwin <[EMAIL PROTECTED]>: > > > > Tobias Gies wrote: > > > > as we approach 2.0, we will have to think of a way to report deprecated > > class or method calls to the developer. > > > > Does this really need a new component? What's wrong with > trigger_error(E_USER_NOTICE)? This seems a lot simpler and more concise. > > It also satisfies your goal of eliminating the tedium of resolving one > exception at a time. Notices are not fatal; you can get a bunch of them > during one execution. > > People who want to filter out the notices can do: > error_reporting(error_reporting() & ~E_USER_NOTICE); > ...either in their bootstrap or else in php.ini. > > Regards, > Bill Karwin > -- > View this message in context: > http://www.nabble.com/Zend_Deprecation-is-ready-for-community-review.-tp18513175p18514041.html > Sent from the Zend Framework mailing list archive at Nabble.com. > >
