Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:17506
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <42EFE41F.9040400@safesearching.com>
Date: Tue, 02 Aug 2005 14:22:39 -0700
User-Agent: Mozilla Thunderbird 1.0+ (Windows/20050531)
MIME-Version: 1.0
To: internals@lists.php.net
References: <Pine.LNX.4.62.0508021457590.2808@localhost>
In-Reply-To: <Pine.LNX.4.62.0508021457590.2808@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Property Overloading RFC
From: james@safesearching.com (James Crumpton)

My concern with the self::isVirtual() syntax would be...

class Base {
     function __get($name) {
         if (!self::isVirtual($name))
             throw;
     }
}

class Foo {
     abstract public $bar = 1;
}

$f = new Foo;
echo $f->bar;

... Are these 'virtual' members going to work like static members, in that using 
self:: in a base class doesn't allow access to those static members of 
inheriting classes? ie, will the above example throw an error or not, like it 
would if a similar thing with statics were to try and be done.

Derick Rethans wrote:

 >   This is ofcourse overly complicated. A better workable solution would be -
 >   without breaking BC (suggestions for syntax here are very welcome):
 >
 > <?php
 > class Base
 > {
 >     abstract public $x = 1;
 >
 >     function __get($name)
 >     {
 >         if (!self::isVirtual($name))) {
 >             /* throw error */
 >         }
 >     }
 > }
 >
 > $b = new Base();
 > echo $b->foo;
 > ?>