Re: Why change require_once? A brief explanation of motives
| From: | Lukas Kahwe Smith | Date: | Tue, 17 Jul 2007 15:45:18 +0000 |
| Subject: | Re: Why change require_once? A brief explanation of motives | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-47575@lists.php.net to get a copy of this message | ||
Philippe Jausions wrote:
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?)AFAIK IDE's just index the code on a per directory basis. I do not think that they follow require_once etc. I will shoot out an email to ActiveState and Zend guys on this.
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?Yeah, I agree that its magical, however instead of grepping for require_once calls, I guess you now need to grep for "new foobar" or just "foobar" aka the class name. I did not catch the thing about xdebug, I will ask Derick about this. regards, Lukas