Re: Rethink CS for require_once?

bertrand Gugger wrote:

Hi, I'm puzzled, so I come back to it again, Greg Beaver wrote:

Hi, I would like to suggest a simple and compelling change into the CS for require_once in PEAR packages.

Don't blame if I'm bloody, I try to understand what you suggest. Is it: You want to have all sub "internal" required php to be relative not to the PEAR translation but to the location of the basic requiring pear package ? I retain that user scripts and require of external pckgs MUST still say 'require_once'

yes, exactly. I don't think it is wise to introduce any PEAR-wide dependencies on loading methods. Nothing should hamper the user's ability to write his or her own __autoload() function, as this is an application-level option, and not a package-level option. Greg