[wp-trac] [WordPress Trac] #18453: Improved doing_it_wrong()

[WordPress Trac]

#18453: Improved doing_it_wrong()
-------------------------+-----------------------------
 Reporter:  azaozz       |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Future Release
Component:  General      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  close        |
-------------------------+-----------------------------

Comment (by nacin):

 Reading #18512 and the patch from Chris, I think I still agree this is
 plugin material for now. How expensive is a backtrace? I don't think I'd
 like this running on every pageload, even with WP_DEBUG.

 I'm tempted to include a link to the Debug Bar plugin in wp-config-
 sample.php where we reference WP_DEBUG, and maybe even in every
 trigger_error() in the _deprecated_* and _doing_it_wrong() functions. Or a
 link to codex.wordpress.org/Debugging_in_WordPress which can pimp things
 like WP_DEBUG, the Debug Bar, and Log Deprecated Notices.

 Other than performance, the other issue is that the backtrace is going to
 lie, pretty often, depending on how it is used in the plugin and how the
 notice is triggered in core.As pointed about above, the code from LDN is
 pretty painful.

 I'd be happy to revisit this but I'm just not convinced yet.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/18453#comment:5>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software