Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21422 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 27768 invoked by uid 1010); 4 Jan 2006 17:12:16 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 27753 invoked from network); 4 Jan 2006 17:12:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jan 2006 17:12:15 -0000 X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6 Received: from ([81.169.182.136:46284] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id ED/B3-34518-EE10CB34 for ; Wed, 04 Jan 2006 12:12:14 -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 9EB1635C1D8; Wed, 4 Jan 2006 18:12:11 +0100 (CET) Date: Wed, 4 Jan 2006 18:12:13 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <1604138933.20060104181213@marcus-boerger.de> To: Stanislav Malyshev Cc: 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> <1594973025.20060104122023@marcus-boerger.de> <43BBB6A0.1070800@php.net> <43BBD4F6.6070506@php.net> <1728947126.20060104162939@marcus-boerger.de> <1355723992.20060104174634@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, just again, the point is integration so that you know whether it makes any sense to call soemthing or not without having to check for errors after the call. marcus Wednesday, January 4, 2006, 5:59:59 PM, you wrote: MB>>> both will have a function pointer on the c side so the major MB>>>slowdown you spoke of will only be there if one actually wants it. MB>>>Otherwise there will be only the pointer check. > I think you lost me. What exactly you are describing here? I though we > were talking about implementing something alike __call - which is not C > side - and implementing it in PHP, which is not C side either. Obviously, > it is not what do you describe - so can you give some more explanation > what do you mean? > -- > Stanislav Malyshev, Zend Products Engineer > stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115 Best regards, Marcus