Re: protected __call() question
| From: | Andi Gutmans | Date: | Fri, 09 Apr 2004 07:40:10 +0000 |
| Subject: | Re: protected __call() question | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-9020@lists.php.net to get a copy of this message | ||
At 09:40 AM 4/8/2004 +0200, Marcus Boerger wrote:
And I think __call has such few uses (I can think of one class right now: Object proxies for SOAP/ XMLRPC or the like) that you will hardly redeclare it anyway. If you start using __call on a regular basis you should probably rethink your design :-) An iterator may want to "reflect" it's inner object/iterator methods by call. This you may cal aggregation. In other words you can use __call to emulate MI and aggregation.Not only an iterator. I wrote a classic delegation (aggregation) example and it used __call(). Andi