Re: Why change require_once? A brief explanation of motives

From: Date: Wed, 18 Jul 2007 15:40:34 +0000
Subject: Re: Why change require_once? A brief explanation of motives
References: 1 2 3 4 5  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-47611@lists.php.net to get a copy of this message
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.
Just for completeness: "Komodo will use require/include as a last resort, but does not depend on them for completion data. We provide a configuration with which you tell Komodo the paths to any libraries (if outside a project). Files in projects are also automatically used. " regards, Lukas

« previous php.pear.dev (#47611) next »