Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:13783 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88760 invoked by uid 1010); 8 Nov 2004 10:29:15 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 88617 invoked from network); 8 Nov 2004 10:29:14 -0000 Received: from unknown (HELO mail.zend.com) (80.74.107.235) by pb1.pair.com with SMTP; 8 Nov 2004 10:29:14 -0000 Received: (qmail 13716 invoked from network); 8 Nov 2004 10:29:13 -0000 Received: from shire.zend.office (10.1.2.160) by int.zend.com with SMTP; 8 Nov 2004 10:29:13 -0000 Date: Mon, 8 Nov 2004 12:29:13 +0200 (IST) X-X-Sender: frodo@shire.zend.office To: Marcus Boerger cc: internals@lists.php.net In-Reply-To: <15410470363.20041108111833@marcus-boerger.de> Message-ID: References: <1099844772.320.6.camel@localhost> <15410470363.20041108111833@marcus-boerger.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] __call interceptor and static methods From: stas@zend.com (Stanislav Malyshev) MB>> you won't be able to tell from inside __call() whether a static or MB>> non static method was meant. Technically, it's not a big problem IMO - there could be an argument added or some other solution, like presence of $this. MB>>non static method was meant. The same holds for __get() and __set(). MB>>Also if we start using such code we'd need a class constructor. Thus MB>>this dicussion is leading to the following set of new magics: MB>> MB>>__static_get MB>>__static_set MB>>__static_call MB>>__static_construct What do you mean by __static_construct? When do you expect it to be called? And, BTW - if you need to override method calls, etc. for a global object, why not to use singletons? -- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115