Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41254 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52310 invoked from network); 18 Oct 2008 15:45:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Oct 2008 15:45:18 -0000 Authentication-Results: pb1.pair.com header.from=greg@chiaraquartet.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=greg@chiaraquartet.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 208.83.222.18 cause and error) X-PHP-List-Original-Sender: greg@chiaraquartet.net X-Host-Fingerprint: 208.83.222.18 unknown Linux 2.6 Received: from [208.83.222.18] ([208.83.222.18:55845] helo=mail.bluga.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1E/D5-13947-6840AF84 for ; Sat, 18 Oct 2008 11:45:12 -0400 Received: from mail.bluga.net (localhost.localdomain [127.0.0.1]) by mail.bluga.net (Postfix) with ESMTP id AAB6FC10CB5; Sat, 18 Oct 2008 08:44:56 -0700 (MST) Received: from [192.168.0.106] (unknown [76.84.4.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bluga.net (Postfix) with ESMTP id E3E82C10CB4; Sat, 18 Oct 2008 08:44:55 -0700 (MST) Message-ID: <48FA051A.3060503@chiaraquartet.net> Date: Sat, 18 Oct 2008 10:47:38 -0500 User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: nathan@kraya.co.uk CC: Ronald Chmara , internals@lists.php.net, steph@php.net References: <48F86EB4.5080308@kraya.co.uk> <3E52781C-3CD6-4A44-86B7-2682EC25AEA3@opus1.com> <48F9FBDC.9030300@kraya.co.uk> In-Reply-To: <48F9FBDC.9030300@kraya.co.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: [PHP-DEV] UltraSimple Namespace Solution From: greg@chiaraquartet.net (Gregory Beaver) Nathan Rixham wrote: > seen. Personally though I'd love to see stas' #1 get implemented and > "->" used for all functions in a namespace so.. > one::step::two(); //always static method of class > one::step->two(); //always function of namespace. > > But it's still ambiguous (only in a rarely though) - if an object with a > method "two" is assigned to the static variable of a class called one > then problem comes back. First of all, this is not going to happen (voted down). Second of all one::$step is how static variables are accessed, not one::step. So there is no potential for conflict. Greg