Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:13136 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 26252 invoked by uid 1010); 4 Oct 2004 12:34:39 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 26223 invoked from network); 4 Oct 2004 12:34:39 -0000 Received: from unknown (HELO xaxa.search.ch) (195.141.85.117) by pb1.pair.com with SMTP; 4 Oct 2004 12:34:39 -0000 Received: from localhost (localhost [127.0.0.1]) by xaxa.search.ch (Postfix) with ESMTP id 623B56CFBC; Mon, 4 Oct 2004 14:34:38 +0200 (CEST) Received: by xaxa.search.ch (Postfix, from userid 65534) id 30E9B6D8F5; Mon, 4 Oct 2004 14:34:37 +0200 (CEST) Received: from [192.168.1.72] (ultrafilter-i [192.168.85.2]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by xaxa.search.ch (Postfix) with ESMTP id A841B6CFBC; Mon, 4 Oct 2004 14:34:36 +0200 (CEST) Message-ID: <4161435C.8010108@cschneid.com> Date: Mon, 04 Oct 2004 14:34:36 +0200 User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Wez Furlong Cc: Marcus Bointon , PHP internals References: <4e89b426041004051225c86945@mail.gmail.com> In-Reply-To: <4e89b426041004051225c86945@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on xaxa.search.ch X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.64 X-Virus-Scanned: by AMaViS 0.3.12pre8 Subject: Re: [PHP-DEV] Static call detection From: cschneid@cschneid.com (Christian Schneider) Wez Furlong wrote: > If a method is static, you should only ever call it statically. > Doing any other tricks is just plain wrong. I dare to disagree. For tool functions it often makes sense to make them statically callable while you still might want to use them in an object instance context respecting the instance's state. It may seem a bit hacky but I like PHP for being dynamic enough to allow this. Different people use different styles and I wouldn't say "Using exceptions is just plain wrong" even though I don't like them ;-) > If you still want to know the answer, ask the question on the correct > list; what you've asked has nothing to do with hacking on the > internals of PHP in C. He is asking for a mechanism to properly determine the static/non-static status of a call and I assume he also suggests to add such a mechanism in case it doesn't exist so I think your answer should be less hostile as it concerns internals IMHO. - Chris