Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:8032 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79985 invoked by uid 1010); 21 Feb 2004 02:23:20 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 79951 invoked from network); 21 Feb 2004 02:23:20 -0000 Received: from unknown (HELO imf16aec.mail.bellsouth.net) (205.152.59.64) by pb1.pair.com with SMTP; 21 Feb 2004 02:23:20 -0000 Received: from [192.168.1.114] ([68.18.72.175]) by imf16aec.mail.bellsouth.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040221022319.FPUW1830.imf16aec.mail.bellsouth.net@[192.168.1.114]> for ; Fri, 20 Feb 2004 21:23:19 -0500 Mime-Version: 1.0 (Apple Message framework v612) In-Reply-To: References: <1077090830.30573.1.camel@coogle.localdomain> <20040218115421.434ac336@localhost.localdomain> <1077124444.30567.27.camel@coogle.localdomain> <20040218183012.2ad1beb3@localhost.localdomain> <062101c3f645$e317a5e0$8b018552@titan> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-ID: Content-Transfer-Encoding: 7bit Date: Fri, 20 Feb 2004 21:23:20 -0500 To: PHP Development X-Mailer: Apple Mail (2.612) Subject: Re: [PHP-DEV] Re: Static weirdness.. From: lingwitt@bellsouth.net (Herr Witten) Well, calling a static method from an instance breaks down the logic. If it is static, then the instance has absolutely no bearing when calling it. Therefore, it logically makes sense to call only from the class name. Moreover, making a distinction between the method calling syntax begins to make the distinction between class objects and instance objects. I have a class which deals directly with classes and their static methods as if they are objects. This is a powerful notion that still needs more support in the Zend engine. The call for static method should be: ClassName->method(); Herr Witten > C++ allows $a->bar() when bar() is a static method (yes, it is called > in a static context there too). > > IMO, there should be no error, warning or notice here.