Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21396 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50165 invoked by uid 1010); 4 Jan 2006 09:19:31 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 50150 invoked from network); 4 Jan 2006 09:19:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jan 2006 09:19:31 -0000 X-Host-Fingerprint: 82.94.239.5 jdi.jdi-ict.nl Linux 2.5 (sometimes 2.4) (4) Received: from ([82.94.239.5:54341] helo=jdi.jdi-ict.nl) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id BB/A0-34518-2239BB34 for ; Wed, 04 Jan 2006 04:19:30 -0500 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.12.11/8.12.11) with ESMTP id k049JQJw029836; Wed, 4 Jan 2006 10:19:26 +0100 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.12.11/8.12.11) with ESMTP id k049JMoi029816; Wed, 4 Jan 2006 10:19:22 +0100 Date: Wed, 4 Jan 2006 10:19:22 +0100 (CET) X-X-Sender: derick@localhost To: Stanislav Malyshev cc: Marcus Boerger , php internals In-Reply-To: Message-ID: References: <20060103205728.GF26280@desario.homelinux.net> <7.0.0.16.2.20060103154506.043678e8@zend.com> <829348376.20060104010548@marcus-boerger.de> X-Face: "L'&?Ah3MYF@FB4hU'XhNhLB]222(Lbr2Y@F:GE[OO;"F5p>qtFBl|yVVA&D{A(g3[C}mG:199P+5C'v.M/u@Z\![0b:Mv.[l6[uWl' MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at jdi-ict.nl Subject: Re: [PHP-DEV] __call overload detection From: derick@php.net (Derick Rethans) On Wed, 4 Jan 2006, Stanislav Malyshev wrote: > MB>> the point is probably that there is no way in determinig whether a > MB>>certain function is supposed to work prior to calling it. > > This is the case for all functions. For example, if you call mysql_query, > you have no way of knowing if it would succeed prior to calling it. So > __call is not much different - you know it will call __call but you don't > know if the call would succeed. That is not fully true, as you can use function_exists() on mysql_query, where there is no such possibility for methods that are overloaded with __call(). Derick