[wp-trac] [WordPress Trac] #32845: Introduce wp_include()

WordPress Trac noreply at wordpress.org
Thu Jul 2 15:39:46 UTC 2015


#32845: Introduce wp_include()
-----------------------------+-----------------------
 Reporter:  johnjamesjacoby  |       Owner:
     Type:  feature request  |      Status:  reopened
 Priority:  normal           |   Milestone:
Component:  Plugins          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  close            |     Focuses:
-----------------------------+-----------------------
Changes (by jorbin):

 * keywords:   => close


Comment:

 While this is an interesting idea that would improve the flexibility of
 WordPress, I think it is is impractical. If this went in, we would never
 be able to deprecate a function and move it to deprecated.php or
 reorganize any functions across files since it might cause a function
 redeclared fatal error.  The flexibility given to plugins and themes would
 reduce flexibility in core. I don't think that tradeoff is worth it and
 thus suggest we close this as wontfix.

 If an individual needs to be able to declare there own version of an
 include, they can [http://php.net/manual/en/function.set-include-path.php
 modify the php include path] to accomplish that (but i would caution them
 to be very careful in doing so and would strongly discourage doing so in a
 publicly released plugin).

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


More information about the wp-trac mailing list