[TYPO3-50-general] Will Typo3 5.0 use namespaces with PHP 5.3/PHP 6?

[Christoph Blömer]

Robert Lemke schrieb:
> Hi Christoph,
>
> (some note: please don't hijack threads - you just did by replying to 
> the "Discussion to
> CodingStandards" thread)
>
Hi Robert.
Ups, I didn't thought about that, that there is stored some extra 
information in the reply mail. ;-)
So I just write, a new mail to the mailinglist with or w/out 
[TYPO3-50-general] at the beginning of the subject?

> Am 13.01.2008 um 17:39 schrieb Christoph Blömer:
>
>> will Typo3 5.0 use namespaces from PHP 5.3 and PHP 6 instead of the long
>> class names with prefixes?
>
> In fact we have everything prepared from the beginning to be able to 
> switch to namespaces
> as soon as they are supported by PHP. But after the lengthy discussion 
> in the php-internals
> list we have decided to postpone namespaces support a little.
>
> These two requirements must be met before we use namespaces:
>
>   - the namespaces implementation must be stable, be released in a 
> stable PHP version and
>     the features must make sense (the current implementation looks 
> promising).
OK. That should come with version 5.3 of PHP in the next two month (I 
hope ;-))
>   - there must be refactoring tools available which support namespaces.
>     The problem is that if you want to rename or move classes during 
> refactoring, you can't
>     just do a global search & replace if you use the short class names.
>
>     Imagine you want to rename the component manager 
> (T3::Framework::Component::Manager) to
>     component service (T3::Framework::Component:Service). If you just 
> search & replace "Manager"
>     this would end up in a chaos.
That's really a problem. I don't know a lot tools which have the same 
features like a editor for java or C#.
Maybe Zend Studio would be the first. I just saw, that it should be 
availabe as a Eclipse extension (but it's not freeware :-( ). Or is 
there anything for Eclipse.
> So, in general we really like namespaces, but we'd like to wait a 
> little more until we use it.
> We'll probably do so before having a final 1.0 release of the framework.
>
> robert