Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:17614
Return-Path: <andrei@gravitonic.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 1568 invoked by uid 1010); 8 Aug 2005 16:55:54 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 1553 invoked from network); 8 Aug 2005 16:55:54 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 8 Aug 2005 16:55:54 -0000
X-Host-Fingerprint: 216.145.54.171 mrout1.yahoo.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2)
Received: from ([216.145.54.171:39569] helo=mrout1.yahoo.com)
	by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP
	id A6/47-04646-A9E87F24 for <internals@lists.php.net>; Mon, 08 Aug 2005 12:55:54 -0400
Received: from [66.228.175.145] (borndress-lm.corp.yahoo.com [66.228.175.145])
	by mrout1.yahoo.com (8.13.4/8.13.4/y.out) with ESMTP id j78GqrJo078607;
	Mon, 8 Aug 2005 09:52:55 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.62.0508040907550.2808@localhost>
References: <Pine.LNX.4.62.0508021457590.2808@localhost> <39FD64FE-3B15-4E66-A4CD-C392B666BD32@gravitonic.com> <Pine.LNX.4.62.0508040907550.2808@localhost>
Mime-Version: 1.0 (Apple Message framework v622)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-ID: <7024df2a703d613774741267491e6a09@gravitonic.com>
Content-Transfer-Encoding: 7bit
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>
Date: Mon, 8 Aug 2005 09:52:52 -0700
To: Derick Rethans <dr@ez.no>
X-Mailer: Apple Mail (2.622)
Subject: Re: [PHP-DEV] Property Overloading RFC
From: andrei@gravitonic.com (Andrei Zmievski)

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.

> Works for me, but it needs to be able to called statically (::) and
> dynamically (->).

Shouldn't be a problem, should it?

-Andrei