Since the writing of my namespace post things have changed. The voting is in (so it’s said) and the new namespace separator is the backslash “\” character. That’s right, the escape sequence character.
This is caused an uproar in the community and I’m personally not a fan of it. At the same time (and after many weeks of debating), I have decided to support this effort. While I’m not a fan of its implementation, I’m still pleased that namespace functionality is being implemented into PHP.
Your thoughts?
![[del.icio.us]](http://www.phpfever.com/wp-content/plugins/bookmarkify/delicious.png)
![[Digg]](http://www.phpfever.com/wp-content/plugins/bookmarkify/digg.png)
![[Google]](http://www.phpfever.com/wp-content/plugins/bookmarkify/google.png)
![[LinkedIn]](http://www.phpfever.com/wp-content/plugins/bookmarkify/linkedin.png)
![[StumbleUpon]](http://www.phpfever.com/wp-content/plugins/bookmarkify/stumbleupon.png)
![[Windows Live]](http://www.phpfever.com/wp-content/plugins/bookmarkify/windowslive.png)
![[Yahoo!]](http://www.phpfever.com/wp-content/plugins/bookmarkify/yahoo.png)
![[Email]](http://www.phpfever.com/wp-content/plugins/bookmarkify/email.png)
Orgapolanko Detroit Rothschild : 05 December 2008 at 1:07 pm
Totally ILL. This finally is the last thing that kicked our whole work over to python, definitely. We are changing abou 20 old customer sites to python now, because ignorance and narrowmindedness of these php freaks.
look here:
Java:
Attribute/Method access: foo.bar
Static method access: Foo.bar
Package access: foo.bar.baz
C#:
Attribute/Method access: foo.bar
Static method access: Foo.bar
Namespace access: foo.bar.baz
Python:
Attribute/Method access: foo.bar
Static method access: Foo.bar
Module access: foo.bar.baz
PHP:
Attribute/Method access: $foo->bar
Static method access: Foo::bar
Namespace access: foo\bar\baz
Will Fitch : 05 December 2008 at 1:19 pm
I feel your pain, my friend. But i’m not ready to give on PHP yet!