Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21386 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 1630 invoked by uid 1010); 4 Jan 2006 01:29:19 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 1615 invoked from network); 4 Jan 2006 01:29:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jan 2006 01:29:19 -0000 X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from ([80.74.107.235:46796] helo=mail.zend.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 81/60-34518-EE42BB34 for ; Tue, 03 Jan 2006 20:29:19 -0500 Received: (qmail 1567 invoked from network); 4 Jan 2006 01:29:13 -0000 Received: from localhost (HELO ANDI-NOTEBOOK.zend.com) (127.0.0.1) by localhost with SMTP; 4 Jan 2006 01:29:13 -0000 Message-ID: <7.0.0.16.2.20060103172755.043983a0@zend.com> X-Mailer: QUALCOMM Windows Eudora Version 7.0.0.16 Date: Tue, 03 Jan 2006 17:29:11 -0800 To: Marcus Boerger Cc: Andrew Yochum , php internals In-Reply-To: <1789719273.20060104022450@marcus-boerger.de> References: <20060103205728.GF26280@desario.homelinux.net> <7.0.0.16.2.20060103154506.043678e8@zend.com> <829348376.20060104010548@marcus-boerger.de> <7.0.0.16.2.20060103164047.043e6900@zend.com> <1789719273.20060104022450@marcus-boerger.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: [PHP-DEV] __call overload detection From: andi@zend.com (Andi Gutmans) I think it's different especially as it's complementary to unset() but I don't intend to get into an argument about it. In any case, the tools for Andrew to resolve this programmatically on the PHP level exist even if the syntax isn't 100% of what he'd like it to be. Over and out. Andi At 05:24 PM 1/3/2006, Marcus Boerger wrote: >Hello Andi, > > we didn't saw any necessaty for __isset either. > >marcus > >Wednesday, January 4, 2006, 1:41:44 AM, you wrote: > > > Right but you can do it in user-land. If you're writing __call() you > > could add an additional method to see if it's mapped. I don't think > > it's quite as common as isset(). > > > > > At 04:05 PM 1/3/2006, Marcus Boerger wrote: > >>Hello Andi, > >> > >> the point is probably that there is no way in determinig whether a > >>certain function is supposed to work prior to calling it. > >> > >>regards > >>marcus > >> > >>Wednesday, January 4, 2006, 12:45:23 AM, you wrote: > >> > >> > Why not just use Reflection API to check? It seems quite > trivial to do so. > >> > >> > At 12:57 PM 1/3/2006, Andrew Yochum wrote: > >> >>Currently there is no way to detect if the __call overloads a particular > >> >>method. Property overloading has __isset now in 5.1 - maybe for method > >> >>overloading the equivalent should be something like __iscallable. Maybe > >> >>method_exists should remain as is, as the method won't ever really exist > >> >>but is_callable would/could use it, or perhaps some new function.