Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:661 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 53884 invoked from network); 4 Apr 2003 14:53:10 -0000 Received: from unknown (HELO localhost.localdomain) (65.198.110.5) by pb1.pair.com with SMTP; 4 Apr 2003 14:53:10 -0000 Received: (from andrei@localhost) by localhost.localdomain (8.11.6/8.11.6) id h34Eqbg32713; Fri, 4 Apr 2003 09:52:37 -0500 X-Authentication-Warning: localhost.localdomain: andrei set sender to andrei@gravitonic.com using -f Date: Fri, 4 Apr 2003 09:52:37 -0500 To: PHP Internals , engine@lists.zend.com Message-ID: <20030404145236.GA32691@hyperion.gravitonic.com> Mail-Followup-To: Andrei Zmievski , PHP Internals , engine@lists.zend.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: Static and non-static methods From: andrei@gravitonic.com (Andrei Zmievski) What does everyone think about disallowing non-instance calls to methods which are not declared static? Currently, this works: class A { function B() { return 1; } } A::B(); But really, if B was intended to be used that way, it should have been declared as static. -Andrei http://www.gravitonic.com/ * If it ain't broken, it doesn't have enough features yet. *