Re: Inconsistencies in 5.3

From: Date: Wed, 13 Aug 2008 17:43:42 +0000
Subject: Re: Inconsistencies in 5.3
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15  Groups: php.internals 
Request: Send a blank email to internals+get-39923@lists.php.net to get a copy of this message
Hello Lars, Wednesday, August 13, 2008, 3:35:32 PM, you wrote: > Hi Markus > Am Mittwoch, den 13.08.2008, 15:21 +0200 schrieb Marcus Boerger: > [...] >> Namespaces are new, so it never worked before. But yes, this would trigger >> a warning in the compiler which means you are told to not do this with apc >> or other compiler caches. > You are aware that this is used in a number of PHP libraries/frameworks? > Additionally, a lot have code like this: Once again, no code can trigger the warning right now. As the warning requires a namespace before it can be triggered. Autoload should be declared outside a namespace so that it can load correct namespace classes anyway. So I do not see an issue here. > class ... > public function foo() > { > if (!$this->_something) { > require_once 'Foo/Exception.php'; > throw new FooException(); > } > } > I guess most of the time those using OP caches know what they are doing. > So why should a warning be triggered here? > cu, Lars Best regards, Marcus

« previous php.internals (#39923) next »