-- till <[EMAIL PROTECTED]> wrote (on Friday, 18 July 2008, 03:13 PM -0400): > On Fri, Jul 18, 2008 at 3:02 PM, Matthew Weier O'Phinney > <[EMAIL PROTECTED]> wrote: > > -- Lars Strojny <[EMAIL PROTECTED]> wrote > > (on Friday, 18 July 2008, 03:11 PM +0200): > >> Hi Tobias, hi Bill, > >> > >> Am Donnerstag, den 17.07.2008, 10:42 -0700 schrieb Bill Karwin: > >> > Does this really need a new component? What's wrong with > >> > trigger_error(E_USER_NOTICE)? This seems a lot simpler and more > >> > concise. > >> > >> In PHP 5.3 we will even have E_DEPRECATED as an error level. > > > > However, this is an engine-level error level -- you cannot trigger it > > from userland code. Additionally, we need to consider how we mark > > deprecation _before_ 5.3. > > I am just wondering whatever happened to reading documentation? I > mean, phpdoc probably allows us to generate another table view with > all the info on deprecated classes/methods, so I am not sure > implementing another component to cater lazyness is really necessary. > :D > > Really provoking, I know. ;)
I'm not convinced we need a component -- we simply need to choose a standard way to mark deprecation. Marking items deprecated in the API docs is all fine and dandy, but it doesn't put it right in front of the developer the way a triggered error or exception does. Developers can't be trusted to read the documentation, in my experience.... and having a big, nasty warning in their logs or display will get their attention much better than notes in the API docs. :) -- Matthew Weier O'Phinney Software Architect | [EMAIL PROTECTED] Zend Framework | http://framework.zend.com/
