Re: [Coding Standards] Loading all files at once

Hi, I read/skimmed most of the post in this thread. I just wanted to make it clear again what the idea here is: 1) The idea is to provide an optimized solution for multiple "audiences": - speed freaks - unzip and go types - maintenance flexibility freaks Speed freaks will want to include all code with absolute paths without "_once", unzip and go types do not like to mess with the include_path and maintenance flexibility freaks appreciate the ability of easily overriding library implementations by placing a custom version before the lib in the include path. 2) Now the current system was incompatible with the first 2 types. The proposed solution should be compatible with all 3 types. We will provide them with the necessary implementations in order for them to define an autoload callback function or with an easy way to load what they need in a single require call. 3) I have not looked at the wiki page since skimming the initial version, but Alexey is right that any decision should always be presented including the goals and other reasoning (links etc.). The default is to allow everything, every reduction in freedom must have a reason. More importantly the reason need to be documented for future generations :) regards, Lukas