Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20874
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: <internals@lists.php.net>
Date: Tue, 29 Nov 2005 23:53:25 -0800
Message-ID: <000601c5f583$2490afb0$5d54edc6@jake>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C5F540.166D6FB0"
Thread-Index: AcX1gySCY/RzuBPASfSzMNPCKiNLuQ==
Subject: Desired namespace behavoir
From: me@bobsilva.com ("Bob Silva")

------=_NextPart_000_0007_01C5F540.166D6FB0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Looking for some feedback on what the expected behavior should be for class
and/or constant ambiguity within namespaces. For instance:

 

Classes.php:

 

namespace A {

    const FOO = 123;

    class Bar { . }

    class FooBaz { . }

}

 

namespace B {

    const FOO = 456;

    class Bar { . }

    class FooBar { . }

}

 

class Bar { . }

define('FOO', 789);

 

File.php:

 

import namespace A;

import namespace B;

 

 

$c = new Bar(FOO); // ambiguous classname/constant

 

Compile-time error on namespace B import? Or runtime error on ambiguous
class creation?

 

Jessie, how does your patch handle it? 

 

Looking at the modules patch, it appears to be a compile time error when the
second class is defined since it is based on zend_class_entry and
CG(class_tables).

 

 

Also, neither patch has scoped imports, they are global. Is this the
"preferred" method? Maybe it's the only method, not sure yet, still
scratching the surface here.

 

Bob


------=_NextPart_000_0007_01C5F540.166D6FB0--