Re: [PEPr] Comment on RFC::Prefix all packages with P_
| From: | Alan Knowles | Date: | Wed, 19 Jul 2006 09:19:16 +0000 |
| Subject: | Re: [PEPr] Comment on RFC::Prefix all packages with P_ | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-43525@lists.php.net to get a copy of this message | ||
Markus Tacker wrote:
> Hoi Alan,
>
> On 7/19/06, Alan Knowles <alan@akbkhome.com> wrote:
>> You realize that make writing code editors a nightmare ;)
>> autocompletion/code hinting etc. will never work....
>
> Hm, I not into this. But does the code hinter really know about class
> trees or just about with classname has which methods?
It will do when I get back to writing it ;)
It parses the include / require calls, has a list of include paths, and
can load any PEAR style require_once / include.
in reality, variable class includes will confuse it no end. -
autoloaders even more... - but at present, this situation is a
minority/edge case, if you autoload everything, it ends up being very
messy...
>
> Anyway we have talked about requiring the extending of an interface
> class with the name of the prefix. This would fix your issue, wouldn't
> it?
>
Not sure how that helps you - if you autoload the interface, you have
the same problem...
Regards
Alan