————- foo.php —————-

function foo() {}

————- bar.php —————-

function bar() {}

————- index.php ————–

// static namespace syntax
MyNamespace::include(’foo.php’);
MyNamespace::include(’bar.php’);
MyNamespace::foo();
MyNamespace::bar();

// dynamic namespace syntax
$my_namespace->include(’foo.php’);
$my_namespace->include(’bar.php’);
$my_namespace->foo();
$my_namespace->bar();

// alternative syntax
include ‘foo.php’ in $my_namespace;

// directory includes
recursive_include($wordpress_namespace, ‘lib/wordpress’);
recursive_include($mediawiki_namespace, ‘lib/mediawiki’);

————————————–

The syntax has some problems, but the idea is clear:
Responsibility for nameclashes is moved to the user code. Existing code can be namespaced from outside.

Why am I writing this here?
Because I did not find another place..

The one downside to your idea is that it requires rewriting “class” and I’m sure that’s a bigger project than they were hoping to take on to get namespaces implemented.

Right now, Dmitry Stogov’s patch is still the leading one, but it’s not without controversy.

For example something like :
class AA::BB::CC {
}
class AA::BB::DD {
}
class AA::EE::CC {
}

$c1 = new AA::BB::CC();
$c2 = new AA::EE::CC();

Pretty simple, no ?

It could work even for non-OOP:
function AA::BB::func($param) {
}
const ZZ::YY::C = “foo”;

AA::BB::func(ZZ::YY::C);