Everything
php
Learn Community Releases The PHP Project
Home » Project » Newsgroups » php.internals » FW: Simple Namespace Proposal »

FW: Simple Namespace Proposal

php.internals

Dmitry Stogov

19 years ago
I am going to commit this patch on Wednesday. Thanks. Dmitry.

Markus Fischer

19 years ago
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, as only being a general lurker on this list, I remmeber when Namespaces came up the first time, there were some technical problems (or just syntactical sugar ones?) with the "::" operator also being used as a namespace separate additional being a class separator. How has this been handled or are there some caveats to watch for? thank you, - - Markus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGmG1/1nS0RcInK9ARAlMBAJ9ixpfVZ4GZQF8u0Lgd+HJall9pLgCgo9gA ogZkPQ+mgJcDxESEYGizkYs= =9OAV -----END PGP SIGNATURE-----

Markus Fischer

19 years ago
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm eager to try this new feature our but I'm dependent on the win32 built from snaps which unfortunately currently doesn't build (the last build was before the namespace commits). It seems the other platforms currently don't build either. thanks - - Markus Markus Fischer wrote:
> Hi, > > as only being a general lurker on this list, I remmeber when Namespaces > came up the first time, there were some technical problems (or just > syntactical sugar ones?) with the "::" operator also being used as a > namespace separate additional being a class separator. > > How has this been handled or are there some caveats to watch for? > > thank you, > - Markus
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGm75U1nS0RcInK9ARAkn1AJ9VLFG6jfG99ZS7IywSYq85CZHV3ACgrJnh xK+jmqw9NHdsrNm1AmiXXo4= =ZtSv -----END PGP SIGNATURE-----

Markus Fischer

19 years ago
Hi, as only being a general lurker on this list, I remember when Namespaces came up the first time, there were some technical problems (or just syntactical sugar ones?) with the "::" operator also being used as a Namespace separate additional being a class separator. How has this been handled or are there some caveats to watch for? thank you, - Markus

Stanislav Malyshev

19 years ago
> as only being a general lurker on this list, I remember when Namespaces > came up the first time, there were some technical problems (or just > syntactical sugar ones?) with the "::" operator also being used as a > Namespace separate additional being a class separator. > > How has this been handled or are there some caveats to watch for?
There's still some ambiguity in cases like Foo::bar() but since we explicitly import namespace shortcut names we always know if there's an import name that can be substituted or class name. This means some slowdown in "hard" cases since we have to first check for import and then for class name but it's compile-time.
-- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com