Re: protected __call() question
| From: | Marcus Boerger | Date: | Tue, 06 Apr 2004 18:27:25 +0000 |
| Subject: | Re: protected __call() question | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-8950@lists.php.net to get a copy of this message | ||
Hello Ferdinand,
that seems to be the current argument - but we have changed otehr places
like that already so we should make this feature request or even bug.
marcus
Monday, April 5, 2004, 1:18:57 PM, you wrote:
> On 5 Apr 2004 at 11:23, Derick Rethans wrote:
>> It is called from a public function, how can that be outside of the
>> class' point of view?
>>
>> Derick
> Ah, now I understand your point. But __call() is called by the engine,
> not by setup(), so it is the outside world....
> Class CallMe
> {
> public function setup()
> {
> $this->fakeMethod();
> }
> protected function __call($method, $params)
> {
> echo 'you called CallMe::'.$method."\n";
> }
> }
> --
> Ferdinand Beyer
> <fb@fbeyer.com>
--
Best regards,
Marcus mailto:helly@php.net