Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41434 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47305 invoked from network); 27 Oct 2008 11:02:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Oct 2008 11:02:24 -0000 Authentication-Results: pb1.pair.com smtp.mail=tom@vector-seven.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=tom@vector-seven.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain vector-seven.com from 67.207.131.5 cause and error) X-PHP-List-Original-Sender: tom@vector-seven.com X-Host-Fingerprint: 67.207.131.5 67-207-131-5.slicehost.net Received: from [67.207.131.5] ([67.207.131.5:48080] helo=vector-seven.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 32/CA-34199-EBF95094 for ; Mon, 27 Oct 2008 06:02:24 -0500 Received: from laptop (210-84-8-111.dyn.iinet.net.au [210.84.8.111]) (Authenticated sender: tom) by vector-seven.com (Postfix) with ESMTPSA id BD349842C0; Mon, 27 Oct 2008 11:02:19 +0000 (UTC) Received: from localhost ([127.0.0.1]) by laptop with esmtp (Exim 4.69) (envelope-from ) id 1KuPrd-0003Gt-WC; Mon, 27 Oct 2008 22:02:26 +1100 Message-ID: <49059FC1.2060702@vector-seven.com> Date: Mon, 27 Oct 2008 22:02:25 +1100 User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: Lester Caine CC: PHP internals References: <49047D62.1030900@lsces.co.uk> In-Reply-To: <49047D62.1030900@lsces.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RE: From: tom@vector-seven.com (Thomas Lee) Lester Caine wrote: > The backslash is not ideal, but I think we all need to get behind it > rather than complaining. The only other real alternative today is to > shelve namespaces altogether for the next release rather than putting > something in that is simply not practical to extend later? I'd prefer to see it shelved for another release with the aim of fixing whatever technical barriers made the syntax unworkable in the first place. I'm sure you'd have plenty of volunteers. My personal concern is that once this goes public, we (the end users) are stuck with that decision for the forseeable future. I think there's obviously enough unhappy campers here that this option should be at least considered. Not that I'm holding my breath or anything. Everybody seems to be getting awfully emotional about this ... Cheers, T