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

WordPress Trac noreply at wordpress.org
Thu Apr 21 17:12:28 UTC 2016


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

Comment (by dnaber-de):

 > When you start calling spl_autoload_register directly, though, and you
 provide a way for plugins to provide classes of their own, you quickly
 move into a space where plugin authors need or desire to introduce
 dependencies of their own.

 We are already there. And yes, I totally agree, just having an autoloader
 doesn't solve this problems. But I wouldn't have started this ticket if I
 see a realistic chance to get composer support in the next view years.
 Having an autoloader in core would allow developers at least to use a
 shared instance that can be optimized somehow.

 The proposal is designed flexible and extensible, so in the future it
 wouldn't be a problem to adapt the composer autoloader or the other way
 around.

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


More information about the wp-trac mailing list