Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21421 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 26482 invoked by uid 1010); 4 Jan 2006 17:11:01 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 26466 invoked from network); 4 Jan 2006 17:11:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jan 2006 17:11:01 -0000 X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6 Received: from ([81.169.182.136:46274] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 36/83-34518-4A10CB34 for ; Wed, 04 Jan 2006 12:11:00 -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 BF17235C1D8; Wed, 4 Jan 2006 18:10:57 +0100 (CET) Date: Wed, 4 Jan 2006 18:10:59 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <1665499484.20060104181059@marcus-boerger.de> To: Stanislav Malyshev Cc: Lukas Smith , 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> <1147247476.20060104130117@marcus-boerger.de> <834861041.20060104174811@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, the point is integration but i see no point for further dicussion unless you are willing to reread the thread and accept what we were talking about here. Wednesday, January 4, 2006, 6:02:41 PM, you wrote: MB>>> having non supported dynamic calls behave in the same way as build MB>>>in or user code methods. > As defined code methods? Make your __call always return true and that is > what you'd get, not? Or you want it to behave as undefined methods? Then > make your __call to throw and error once it can not call a function and > you get the same. Best regards, Marcus