On Aug 30, 2013, at 10:25 AM, Stas Malyshev <[email protected]> wrote:
>
>> Furthermore, I think that's up to the community to decide how to do.
>> They mostly settled on a 1-class-to-1-file rule (which was not the case
>> prior to __autoload/spl_autoload). I am fully confident that they will
>> find a way that makes sense, if given the ability.
>
> This sounds like a solution in search of a problem. I don't think we
> should create solutions for problems that do not exist and then tell
> people "now go find some problem that may fit this neat code that I've
> added to the engine". We should first identify the need and only then
> mess with the engine, not the other way around.
>
The problem exists: us users need a way to better organize our procedural codebases than manually
managing a million require statements. You guys have now given us importing of functions, which is a
great step forward. But we still need a way to intelligently load them.
Attachment: [application/pgp-signature] Message signed with OpenPGP using GPGMail signature.asc