Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21410 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 25756 invoked by uid 1010); 4 Jan 2006 13:55:39 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 25741 invoked from network); 4 Jan 2006 13:55:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jan 2006 13:55:39 -0000 X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from ([80.74.107.235:4144] helo=mail.zend.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 1F/E7-34518-9D3DBB34 for ; Wed, 04 Jan 2006 08:55:38 -0500 Received: (qmail 21806 invoked from network); 4 Jan 2006 13:55:33 -0000 Received: from shire.zend.office (10.1.2.160) by internal.zend.office with SMTP; 4 Jan 2006 13:55:33 -0000 Date: Wed, 4 Jan 2006 15:55:33 +0200 (IST) X-X-Sender: frodo@shire.zend.office To: Lukas Smith cc: Marcus Boerger , php internals In-Reply-To: <43BBB6A0.1070800@php.net> Message-ID: 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> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] __call overload detection From: stas@zend.com (Stanislav Malyshev) LS>>I think its obvious that you can implement things in userland or inside the LS>>engine. The main advantage of doing it inside the engine is that it then LS>>becomes the standard way of doing things, where as with userland its likely LS>>that several competing "standards" will emerge. Not because of real LS>>advantages, but just because of lack of a central standard. I don't see anything there to be implemented in the engine. What exactly you want the engine to do? Only thing I can see is to support it in is_callable() - I'm not sure if it worth it but we can do so that is_callable would check if the object has __callable function or implements interface CallableCheck or whatever and if it has, call it. Though I'm not sure it really worth the hassle - all three people that need it in real world probably already implemented it in userland anyway. -- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115