[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 MikeSchinkel):

 Replying to [comment:209 schlessera]:
 > But if we ... start to discuss implementation details, file naming
 conventions, folder layout, etc... we will just end up with a "spaces-vs-
 tabs" debate and this will go nowhere.

 Will we really?  My opinions will be driven by the factual benefits of any
 given approach. Hopefully others will do the same. Or said another way, I
 don't really care about what they are as long as they empower autoloading
 and ideally dynamic discovery.

 That said, the file naming conventions, folder layout are not super
 important '''other than that we have something''' so that we can refactor
 the existing classes to make them autoloadable.  We can always change the
 file naming conventions folder layouts before code is shipped.

 > I have my own ideas about what layout and naming schemes would make
 sense for WordPress. But this ticket is complicated enough as it is, we
 don't need to add more factors.

 Then please tell me what your proposal is to move things forward to
 address the things we all can agree on?

 Without a viable alternative or condemnation from the core contributors
 here the best thing to do is move forward and start creating patches
 because actual code is more actionable than circular debates.

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