Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30074
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain php.net from 213.239.212.54 cause and error)
Message-ID: <46659A9E.1020202@php.net>
Date: Tue, 05 Jun 2007 19:17:18 +0200
User-Agent: Thunderbird 1.5.0.7 (X11/20060909)
MIME-Version: 1.0
To: Bart de Boer <bart@mediawave.nl>
CC: Jochem Maas <jochem@iamjochem.com>,  internals@lists.php.net, 
 Ken Stanley <dohpaz@gmail.com>
References: <c70e053d0705261548v63c111a1qf9bfae78534b27da@mail.gmail.com>    <56275.216.230.84.67.1180484964.squirrel@www.l-i-e.com>    <465D9040.6030001@iamjochem.com>    <43689.216.230.84.67.1180643866.squirrel@www.l-i-e.com>    <465FC76B.6030208@mediawave.nl>    <c70e053d0706010543s39dd8575l5cb3b6a46eb6b339@mail.gmail.com>    <4660A44F.6060802@mediawave.nl> <46657E94.1030900@iamjochem.com> <2689.192.87.117.168.1181060919.squirrel@www.mediawave.nl>
In-Reply-To: <2689.192.87.117.168.1181060919.squirrel@www.mediawave.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] late static binding (please break BC?)
From: colder@php.net (Etienne Kneuss)

Bart de Boer wrote:
> I thought late static binding had something to do with accessing static
> _variables_ in child classes. You're currently solving that problem by
> defining a static function getTableName() in the child class. But I think
> that isn't very efficient when you're dealing with complex objects and/or
> arrays which would need to be accessed frequently.
>
> If it were possible your code example could be solved as:
>
> <?php
>
> class Data {
> 	static function findRange() {
> 		if (!child::$tableName)
> 			throw new Exception('WTF');
> 		else
> 			return child::$tableName;
> 	}
> }
>
> class Prod {
> 	static $tableName = 'PRODS';
> }
>
> ?>
>
> But it seems this feature request belongs in a different thread. :)
>
>
>   
Late static binding can also be used to access static properties, of 
course. The same class resolution mechanism is used by foo::$member and 
foo::method(); so the keyword would apply to both.
Same with magic syntax like $a = new self();
>
> Now I understand why this:: might be confusing since it is meant for
> objects. self:: would mean we can't access stuff in the current class
> anymore. What about
>
> derived::
>
> or
>
> extended::
>
> ?
>   

It's always dangerous to introduce a new keyword, as it can/will break 
BC (i.e what if somebody has defined a function derived(), the parser 
would choke on that).

I'm personally fine with static, even if it may eventually introduce 
some confusion.

Regards

-- 
Etienne Kneuss
http://www.colder.ch

Men never do evil so completely and cheerfully as 
when they do it from a religious conviction.
-- Pascal