Re: Why change require_once? A brief explanation of motives
| From: | Philippe Jausions | Date: | Tue, 17 Jul 2007 20:59:00 +0000 |
| Subject: | Re: Why change require_once? A brief explanation of motives | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-47588@lists.php.net to get a copy of this message | ||
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.
>
> Cheers,
> Till
So, would removing *_once calls in the code still allow the IDE to
resolve classes? It's not really a PEAR2 issue per-se, but would need to
be documented if it has an impact.
Is someone with Zend Studio able to do a quick test? and let us know?
-Philippe