rfc:changes_to_include_and_require

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
rfc:changes_to_include_and_require [2012/03/08 16:01]
michaelmorris Dropping one of the two suggestions.
rfc:changes_to_include_and_require [2017/09/22 13:28] (current)
Line 30: Line 30:
  
 This provides a powerful layer of flexibility for frameworks. ​ It also allows a tyro to whack their foot off and spaghetti doesn'​t even begin to describe the situation that will occur if this gets used incorrectly. This provides a powerful layer of flexibility for frameworks. ​ It also allows a tyro to whack their foot off and spaghetti doesn'​t even begin to describe the situation that will occur if this gets used incorrectly.
 +
 +===== 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/​include is forcing upon it?
 +
 +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 (external edit)