Re: Property Overloading RFC
| From: | Derick Rethans | Date: | Tue, 09 Aug 2005 07:18:42 +0000 |
| Subject: | Re: Property Overloading RFC | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-17663@lists.php.net to get a copy of this message | ||
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