Re: Re: namespaces: import name conflicts with defined class

From: Date: Wed, 03 Oct 2007 15:33:21 +0000
Subject: Re: Re: namespaces: import name conflicts with defined class
References: 1 2 3 4 5  Groups: php.internals 
Request: Send a blank email to internals+get-32601@lists.php.net to get a copy of this message
if your exception is so general that it is called exception you can obviously simply use exception.
Maybe _my_ exception is a generic exception in _my_ framework and implements some helper functions i need? But the discussion is not about exceptions, it's about classnames that PHP declares i don't want to care about, because i put my classes in "namespaces". Maybe i don't use DOM and i don't know (i don't want to know) that there is a "XsltProcessor" class, i implemented a xsltprocessor myself, a generic one ;). So i need to name it GenericXsltProcessor because luckily currently there is no other class with that name (yet)? Come on ... Who knows what classes SPL or some pecl extension will declare some day, to me this is like a guarantee that future PHP releases, or extensions, will break applications that use namespaces. Sounds quite ironic to me. regards, Benjamin

« previous php.internals (#32601) next »