Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:17663
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Tue, 9 Aug 2005 09:18:42 +0200 (CEST)
To: Andrei Zmievski <andrei@gravitonic.com>
cc: Raymond Bosman <rb@ez.no>,
	PHP Developers Mailing List <internals@lists.php.net>,
	Jan Borsodi <jb@ez.no>, Frederik Holljen <fh@ez.no>,
	Tobias Schlitt <ts@ez.no>
In-Reply-To: <7024df2a703d613774741267491e6a09@gravitonic.com>
Message-ID: <Pine.LNX.4.62.0508090917390.3884@localhost>
References: <Pine.LNX.4.62.0508021457590.2808@localhost>
	<39FD64FE-3B15-4E66-A4CD-C392B666BD32@gravitonic.com>
	<Pine.LNX.4.62.0508040907550.2808@localhost> <7024df2a703d613774741267491e6a09@gravitonic.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [PHP-DEV] Property Overloading RFC
From: dr@ez.no (Derick Rethans)

On Mon, 8 Aug 2005, Andrei Zmievski wrote:

> On Aug 4, 2005, at 12:09 AM, Derick Rethans wrote:
> 
> > Then you don't do it - it's not a requirement... just an optional thing
> > (and ofcourse you can't do the __have_prop() thing then that you
> > suggested below.
> 
> Why not? _have_prop() should be able to return true if the class does handle
> one of those 1000 properties. They don't need to be declared.

Ah,you meant that __have_prop() should always return the full array of 
things that are supported. That is fine, as long as we can have this 
generated from the "abstract" properties that people declared (so that 
they can be documented properly too).

> > Works for me, but it needs to be able to called statically (::) and
> > dynamically (->).
> 
> Shouldn't be a problem, should it?

Nope.

Derick