Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32629
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain thekid.de from 212.227.126.171 cause and error)
Message-ID: <015801c80660$64613b60$16b2a8c0@unterwegs>
To: <internals@lists.php.net>
References: <fdt38g$dgh$1@sea.gmane.org> <4702777C.2090406@zend.com> <47027B78.5070909@sebastian-bergmann.de>
Date: Thu, 4 Oct 2007 10:27:21 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="ISO-8859-15";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV]  Class Posing
From: thekid@thekid.de ("Timm Friebe")

Hi,

>   public function foo()
>   {
>       $bar    = new Bar;
[...]
>   }
>
> When I want to test the foo() method, I want to stub out the usage of
> the Bar class, for example, and have Bar::doSomething() return a
> pre-configured value instead of performing its normal operation.

This is where you'd start refactoring the above sourcecode. I don't like 
this idea at all, because it really only helps you with testing legacy 
source you might not be able to or do not want to change (want to say: rare 
use-case IMO).

If you really need to intercept construction, you can still weave your 
interception functionality into sourcecode as you'd be doing in any AOP 
library. Simply write a stream wrapper for the file:// stream or add a 
filter to it to intercept all includes and / or requires your legacy code 
might contain and rewrite the sourcecode while loading, replacing "new Foo" 
by "newinstance('Foo')" - this might even be possible in a safe manner by 
using preg_replace.

- Timm