Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:8932 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68389 invoked by uid 1010); 5 Apr 2004 08:13:02 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 68311 invoked from network); 5 Apr 2004 08:13:01 -0000 Received: from unknown (HELO jdi.jdimedia.nl) (212.204.192.51) by pb1.pair.com with SMTP; 5 Apr 2004 08:13:01 -0000 Received: from localhost (localhost [127.0.0.1]) by jdi.jdimedia.nl (8.12.10/8.12.10) with ESMTP id i358Cxxe007794; Mon, 5 Apr 2004 10:12:59 +0200 Date: Mon, 5 Apr 2004 10:12:35 +0200 (CEST) X-X-Sender: derick@localhost To: Marcus Boerger cc: Jochem Maas , PHP internals In-Reply-To: <1981266680593.20040405100222@marcus-boerger.de> Message-ID: References: <407066D8.50005@iamjochem.com> <1981266680593.20040405100222@marcus-boerger.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] protected __call() question From: derick@php.net (Derick Rethans) On Mon, 5 Apr 2004, Marcus Boerger wrote: > Hello Jochem, > > using 'protected' for __call() hides that mechanism from the outside world, > hence the behavior is correct. Just drop protected and it should work as you > expect. But it is not called from the outside world ... Derick