[wp-trac] Re: [WordPress Trac] #5338: Preformance Tweaks for WordPress Trunk Plugin API, plugin.php

[WordPress Trac]

#5338: Preformance Tweaks for WordPress Trunk Plugin API, plugin.php
--------------------------+-------------------------------------------------
 Reporter:  darkdragon    |        Owner:  anonymous
     Type:  enhancement   |       Status:  new      
 Priority:  normal        |    Milestone:  2.4      
Component:  Optimization  |      Version:  2.4      
 Severity:  normal        |   Resolution:           
 Keywords:                |  
--------------------------+-------------------------------------------------
Comment (by darkdragon):

 Yeah, then it should lock those numbers in, which it doesn't. It allows
 for any number, therefore unofficially, any priority number must be
 supported. The documentation states that to keep things standard, but
 without checks in the code, then it really is just an '''suggestion''' on
 what the plugin authors should do and not what they must do. If it was
 something they must do, then an error would have been thrown.

 The point is, if I hook into 11, then I mostly know that it will be
 processed last and if I hook into '0' I can guess that it will be run
 before anything else.

 There is no point arguing this, either we add in the checks or we don't,
 but unless we do, then filling the priority list manually is not an
 option.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/5338#comment:4>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software