Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21402 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81103 invoked by uid 1010); 4 Jan 2006 11:20:28 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 81088 invoked from network); 4 Jan 2006 11:20:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jan 2006 11:20:28 -0000 X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6 Received: from ([81.169.182.136:45559] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 19/63-34518-B7FABB34 for ; Wed, 04 Jan 2006 06:20:27 -0500 Received: from [192.168.1.3] (dslb-084-063-000-198.pools.arcor-ip.net [84.63.0.198]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by strato.aixcept.de (Postfix) with ESMTP id 23F1535C1D9; Wed, 4 Jan 2006 12:20:24 +0100 (CET) Date: Wed, 4 Jan 2006 12:20:23 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <1594973025.20060104122023@marcus-boerger.de> To: Stanislav Malyshev Cc: Derick Rethans , php internals In-Reply-To: References: <20060103205728.GF26280@desario.homelinux.net> <7.0.0.16.2.20060103154506.043678e8@zend.com> <829348376.20060104010548@marcus-boerger.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] __call overload detection From: helly@php.net (Marcus Boerger) Hello Stanislav, but that is a way of having __call that obviously doesn't fit the real world. In a real world application i only implement a few things with call and dislike having all the others implemented automatically also. And the i have to care about error generation while the engine could help me a lot so that my error messages look and behave just like they would if there is no __call. But that would indeed require some __exists() or __implemented() support(). marcus Wednesday, January 4, 2006, 10:24:20 AM, you wrote: DR>>>That is not fully true, as you can use function_exists() on DR>>>mysql_query, where there is no such possibility for methods that are DR>>>overloaded with __call(). > That's correct, of course - this is the whole point of __call - it makes > _any_ function exist. Now, calling these functions may succeed or fail - > just as calling any other functions may succeed or fail. > -- > Stanislav Malyshev, Zend Products Engineer > stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115 Best regards, Marcus