Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:666 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 1915 invoked from network); 4 Apr 2003 15:31:45 -0000 Received: from unknown (HELO jdi.jdimedia.nl) (212.204.192.51) by pb1.pair.com with SMTP; 4 Apr 2003 15:31:45 -0000 Received: from jdi.jdimedia.nl (jdi.jdimedia.nl [212.204.192.51]) by jdi.jdimedia.nl (8.12.4/8.12.4) with ESMTP id h34FVfnv025909; Fri, 4 Apr 2003 17:31:43 +0200 Date: Fri, 4 Apr 2003 17:31:41 +0200 (CEST) X-X-Sender: derick@jdi.jdimedia.nl To: Sterling Hughes cc: Andrei Zmievski , PHP Internals , engine@lists.zend.com In-Reply-To: <1049469044.6067.1.camel@hasele> Message-ID: References: <20030404145236.GA32691@hyperion.gravitonic.com> <1049469044.6067.1.camel@hasele> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] Static and non-static methods From: derick@php.net (Derick Rethans) On Fri, 4 Apr 2003, Sterling Hughes wrote: > On Fri, 2003-04-04 at 09:52, Andrei Zmievski wrote: > > 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. > > > > Well its a BC nightmare, and I don't really see any big advantage. Agreed, breaking BC for this sounds like a bad idea to me. Derick -- "my other box is your windows PC" ------------------------------------------------------------------------- Derick Rethans http://derickrethans.nl/ PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ -------------------------------------------------------------------------