Re: Why change require_once? A brief explanation of motives

Greg Beaver wrote: > Hi all, > > <snip> > Users would simply need to either use allfiles.php, autoload, or if > performance is an issue, they can do: > > <?php > require '/full/path/to/Another/Class.php'; > require '/full/path/to/Blah.php'; > ?> > > and they are good to go, and can turn off APC stat and have efficiency - > ALL interested parties win, use of PEAR skyrockets, and we get a > crapload of new developers in the process to improve things. > > I am happy to discuss any of the proposals and change them, but please > limit your comments to brief and carefully researched comments, FUD is > extremely discouraging and does not help us solve the problems at hand. > > Thanks, > Greg Couple of concerns/questions regarding autoload: 1) Would relying on autoload have any impact on developers/users using an IDE? By that I mean, autocompletion integrated API doc and so forth. (Anybody with experience on the topic?) 2) As with everything *magic* and *convenient*, the drawback of autoload is usually the resulting nightmare when debugging code, and can create a lot of WTF factors. IIRC someone mention something not working with XDebug. How will this be addressed? -Philippe