[wp-trac] [WordPress Trac] #36335: Next generation: core autoloader proposal

[WordPress Trac]

#36335: Next generation: core autoloader proposal
-----------------------------+------------------
 Reporter:  dnaber-de        |       Owner:
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  4.7
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:
-----------------------------+------------------

Comment (by jdgrimes):

 Replying to [comment:147 dnaber-de]:


 I think the primary difference is that in the first case multiple plugins
 can do that, and one can't prevent another from doing so. A plugin can
 even wrap the original object and pass everything that it doesn't
 specifically need to override through to the original object with
 `__call()` and `__get()`. Multiple plugins can do this, likely without
 outright killing the site, though results will probably vary. :-)

 With the second case, once one plugin has included the class, no other
 class of that name can be loaded without a fatal error. So it is a race to
 be first, because only the first to load the class wins.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/36335#comment:148>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform