[news.eclipse.tools.pdt] Re: Requirements for namespace support in PDT

["Michael Spector" <michael@xxxxxxxx>]

We are planning to provide good namespaces support ASAP also. But I think 
it's gonna happen closer to the release of PHP 5.3.

"Karsten Dambekalns" <karsten@xxxxxxxxx> wrote in message 
news:ghttsa$h0i$1@xxxxxxxxxxxxxxxxxxxx
> Hi again.
>
> Now the namespaces syntax has been finalised and alpha3 of PHP 5.3.0 has 
> been released. First projects have switched to the new syntax. One of 
> those projects is our framework FLOW3.
>
> We have tons of code, and auto-completion and error detection were very 
> helpful until namespaces arrived. That's the cost of using bleeding egde, 
> but we have been bleeding for a while now, so... we'd like to have our 
> tools back. At least an IDE that helps, for a start.
>
> Could someone please tell us whether it might make sense to wait for PDT 
> supporting this? I heard from the Apatana people that they will fix[1] 
> their IDE "as soon as possible". That is a lot more promising than *not* 
> saying *anything*.
>
> So, I started this list a while ago, as requested. Any news?
>
> On 16.09.2008 11:06 Uhr, Karsten Dambekalns wrote:
>> As asked by Roy this thread should collect requirements for a useful
>> support of PHP namespaces in PDT (and Zend Studio).
>  ...
>> 1. Make the syntax checker aware of the new keyword.
>> Currently I appear to have more than 11500 errors, but the code
>> works...
>> 2. Make auto completion work again. If I declare some variable to be of
>> type Some::Thing::Here it's members should be offered by auto-
>> completion.
>> 3. Hint on using :: to explicitly specify the global namespace for
>> internal classes (either checking a list of PHP's internal classes or
>> checking against all classes defined in the current namespace.
>> 4. If more than one namespace is used in a file, make it visible in the
>> outline. Maybe even if it's just one namespace.
>
> Regards,
> Karsten
>
> [1] Yes, fix. Namespaces will be a first class language feature with the 
> next PHP version. Not having support for that is a bug IMHO. Think about 
> it.