Re: Why change require_once? A brief explanation of motives

Lukas Kahwe Smith wrote:

Hi Alan etc. What are you arguing against? allfiles as a requirement, and any removal of require_once from where they are supposed to be!

Is having to define that __autoload() function really worth not providing this flexibility? Yes - autoload make the code less clear, it makes optimizing code more difficult as it becomes complex to properly analyze code.

I cant imagine how having a 'flexible' way to load a pear file with code in it, would be a great asset.. - Libraries are just supposed to work, not 'might work if you havent broken your autoload code' Regards Alan

regards, Lukas