Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32552
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ntlworld.com designates 81.103.221.48 as permitted sender)
To: <internals@lists.php.net>
Date: Tue, 2 Oct 2007 15:33:36 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcgE2H3LMvnEkFhWT5+K5wFJxrKE7gAJ9D4g
In-Reply-To: <fdt38g$dgh$1@sea.gmane.org>
Message-ID: <20071002143332.MQJN26699.aamtaout03-winn.ispmail.ntl.com@p2>
Subject: RE: [PHP-DEV]  Class Posing
From: jared.williams1@ntlworld.com ("Jared Williams")
References: <fdt38g$dgh$1@sea.gmane.org>

Ideally think I'd prefer it finer grained... 

interface A
{
}

class AImpl implements A
{
}

	register('A', function() { return new AImpl(); });
	register('Foo', function() { return new Bar(); });
	
	$foo = new Foo();	
	$a = new A();

Would also require functions being values... Which would also be nice. 

J


> -----Original Message-----
> From: news [mailto:news@sea.gmane.org] On Behalf Of Sebastian Bergmann
> Sent: 02 October 2007 10:33
> To: internals@lists.php.net
> Subject: [PHP-DEV] Class Posing
> 
>  From [1]:
> 
>    Objective-C permits a class to wholly replace another 
> class within a
>    program. The replacing class is said to "pose as" the target class.
>    All messages sent to the target class are then instead received by
>    the posing class.
> 
>    There are several restrictions on which classes can pose:
> 
>      * A class may only pose as one of its direct or indirect
>        superclasses.
> 
>      [The other restrictions do not apply to PHP]
> 
>  Earlier this year, Johannes implemented class posing for PHP 
> as follows:
> 
>    <?php
>    class Foo {}
>    class Bar extends Foo {}
> 
>    function new_overload($className)
>    {
>        if ($className == 'Foo') {
>            return new Bar;
>        }
> 
>        // ...
>    }
> 
>    $o = new Foo;
>    // $o is an object of Foo.
> 
>    register_new_overload('new_overload');
> 
>    $o = new Foo;
>    // $o is an object of Bar.
>    ?>
> 
>  We (Johannes, Marcus, Sara, and myself) then discussed where 
> to put this  functionality. Outside of core, there were two 
> places that both make
>  sense: pecl/operator and pecl/runkit.
> 
>  However, to make this a viable mechanism that can be used in 
> tools such  as PHPUnit (for which I could really use this 
> functionality), we agreed  that it actually belongs into the core.
> 
>  Opinions? Needless to say that I would love to see this in 
> PHP 5.3 ;-)
> 
>  --
>  [1] http://en.wikipedia.org/wiki/Objective_C#Posing
> 
> -- 
> Sebastian Bergmann                          
> http://sebastian-bergmann.de/
> GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 
> C514 B85B 5D69
> 
> --
> PHP Internals - PHP Runtime Development Mailing List To 
> unsubscribe, visit: http://www.php.net/unsub.php
>