Re: Namespaces in PHP 6 - ++$take
| From: | Richard Lynch | Date: | Mon, 20 Nov 2006 20:57:59 +0000 |
| Subject: | Re: Namespaces in PHP 6 - ++$take | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-26681@lists.php.net to get a copy of this message | ||
On Fri, November 10, 2006 4:07 pm, Ilia Alshanetsky wrote:
> On 10-Nov-06, at 5:01 PM, Lukas Kahwe Smith wrote:
>> Remember the point Sebastian made earlier. Its also a hassle during
>> development of the library code itself, where you have to deal with
>> endlessly long class names.
>
> You still have the same long names, you've just split them into two
> namespaces + classname rather then just one class name.
This all also rather depends upon the eventual implementation.
I'm sure you're aware that in some languages it is possible to
'import' another namespace and re-name it to NOT conflict with
existing namespaces.
This also allows one to short the name of the namespace if it is
ridiculously long:
import('stupidly_long_brand_aware_name_space_foo.php', 'foo');
That feature may already be "off the table" for PHP in this
discussion, but it may explain this dichotomy of what different
posters are thinking namespaces will "fix" or "not fix"...
--
Some people have a "gift" link here.
Know what I want?
I want you to buy a CD from some starving artist.
http://cdbaby.com/browse/from/lynch
Yeah, I get a buck. So?