Re: Why change require_once? A brief explanation of motives

I've done this on leds and used require* / include* to determine what to use to build autocomplete rules basically because parsing all files on a webdav mounted partition would make the editor very un-responsive, so it performs only the minimal amount of parsing. You can explicitly list other files to include in the include_path list - although I've not updated the code for a while While it's not a very representative sampling (the userbase is probably 2 at most ;) - It gives you an idea of why it's such a problem.. Regards Alan Lukas Kahwe Smith wrote:

till wrote:

On 7/17/07, Lukas Kahwe Smith <mls@pooteeweet.org> wrote:

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.

Yes, they do. Specifically Zend Studio allows you to edit a "php.ini" located in the programs directory to allow "resolving". Then you can also add all class trees (e.g. PEAR, Solar and Zend Framework) to your project by linking the directory and Zend Studio will resolve all require_once calls and enable auto complete/suggest. I have no idea about eclipse - but I'd say it's very similar.

I have gotten the following reply from Zeev: "With Zend Studio there's no attention paid to require() or autoload() or anything else. Any class in your project will be included in the code completion. " I am still waiting on Shane from ActiveState. regards, Lukas