Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20596 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87929 invoked by uid 1010); 26 Nov 2005 22:16:16 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 87911 invoked from network); 26 Nov 2005 22:16:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Nov 2005 22:16:15 -0000 X-Host-Fingerprint: 83.149.123.177 mail.aaaa.ws Linux 2.4/2.6 Received: from ([83.149.123.177:58768] helo=mail.aaaa.ws) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id A2/62-56276-FAED8834 for ; Sat, 26 Nov 2005 17:16:15 -0500 Received: from cpc2-sout5-5-0-cust53.sot3.cable.ntl.com ([81.110.110.53] helo=[192.168.1.103]) by mail.aaaa.ws with esmtpa (Exim 4.50) id 1Eg8L4-0001uz-1k; Sat, 26 Nov 2005 23:16:10 +0100 To: Stanislav Malyshev Cc: internals@lists.php.net In-Reply-To: References: <20.BA.56276.A1BC8834@pb1.pair.com> <4388CE54.6060606@gmail.com> Content-Type: text/plain Date: Sat, 26 Nov 2005 22:16:11 +0000 Message-ID: <1133043371.9056.21.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: namespace separator ideas From: matthew@teh.ath.cx ("Matthew C. Kavanagh") On Sun, 2005-11-27 at 00:06 +0200, Stanislav Malyshev wrote: > I wonder what "PHP feel" is in bunch of special symbols with meaning > entirely obscure to non-initiated... Why not {@ or <* then? They are nice > ASCII art too. And there are so many combinations of two special symbols, > let's find a meaning for all of them. Or at least for as many as we can. Great, everyone loves sarcasm, but you're describing exactly the opposite of what's going on in this thread. There is a perceived need for this functionality and you could argue for or against the functionality instead. There's plenty of two character tokens in PHP already and people aren't calling it "PerlHP" yet. The -> suggestion if practicable seems the most intuitively correct to me.