Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21408 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95441 invoked by uid 1010); 4 Jan 2006 12:02:03 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 95422 invoked from network); 4 Jan 2006 12:02:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jan 2006 12:02:03 -0000 X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6 Received: from ([81.169.182.136:45638] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 6B/05-34518-B39BBB34 for ; Wed, 04 Jan 2006 07:02:03 -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 7B07C35C1D8; Wed, 4 Jan 2006 13:01:57 +0100 (CET) Date: Wed, 4 Jan 2006 13:01:58 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <14810077387.20060104130158@marcus-boerger.de> To: Stanislav Malyshev Cc: Marcus Boerger , 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> 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, where is the relation between __isset and __get/set/unset? marcus Wednesday, January 4, 2006, 12:32:29 PM, you wrote: MB>>> but that is a way of having __call that obviously doesn't fit the real MB>>>world. In a real world application i only implement a few things with call MB>>>and dislike having all the others implemented automatically also. And the MB>>>i have to care about error generation while the engine could help me a lot MB>>>so that my error messages look and behave just like they would if there MB>>>is no __call. But that would indeed require some __exists() or MB>>>__implemented() support(). > Nothing prevents you from having __implemented or __whateveryoulike. > However, I don't see how engine could know beforehand if your __call would > succeed or not, so __implemented has no relation whatsoever to __call, > unless you make this relation in your code - and engine can't know you > did. Best regards, Marcus