rfc:changes_to_include_and_require
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
rfc:changes_to_include_and_require [2012/03/08 16:01] – Dropping one of the two suggestions. michaelmorris | rfc:changes_to_include_and_require [2012/03/12 20:04] – Questions section added (feel free to expand) lynch | ||
---|---|---|---|
Line 30: | Line 30: | ||
This provides a powerful layer of flexibility for frameworks. | This provides a powerful layer of flexibility for frameworks. | ||
+ | |||
+ | ===== Questions ===== | ||
+ | |||
+ | 1) | ||
+ | Is it not possible that the library being pulled contains references to itself in the original namespace, rather than the new sub-namespace the require/ | ||
+ | |||
+ | Or do you anticipate that all such references would be converted? | ||
+ | |||
+ | What if, somehow, the library composes the reference from $data rather than hard-coded? (Which might be kind of crazy, but you know those PHP guys...) | ||
+ | |||
+ | 2) Add more questions. | ||
===== Changelog ===== | ===== Changelog ===== |
rfc/changes_to_include_and_require.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1