Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:49980 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68933 invoked from network); 30 Oct 2010 01:12:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Oct 2010 01:12:14 -0000 Authentication-Results: pb1.pair.com smtp.mail=wrowe@rowe-clan.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=wrowe@rowe-clan.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain rowe-clan.net from 64.202.165.181 cause and error) X-PHP-List-Original-Sender: wrowe@rowe-clan.net X-Host-Fingerprint: 64.202.165.181 smtpauth01.prod.mesa1.secureserver.net Linux 2.4/2.6 Received: from [64.202.165.181] ([64.202.165.181:55626] helo=smtpauth01.prod.mesa1.secureserver.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FF/E8-06635-CE07BCC4 for ; Fri, 29 Oct 2010 21:12:13 -0400 Received: (qmail 23855 invoked from network); 30 Oct 2010 01:12:09 -0000 Received: from unknown (76.252.112.72) by smtpauth01.prod.mesa1.secureserver.net (64.202.165.181) with ESMTP; 30 Oct 2010 01:12:09 -0000 Message-ID: <4CCB70CE.90901@rowe-clan.net> Date: Fri, 29 Oct 2010 20:11:42 -0500 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: internals@lists.php.net References: <4CCB6B21.1070708@codeangel.org> In-Reply-To: <4CCB6B21.1070708@codeangel.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON From: wrowe@rowe-clan.net ("William A. Rowe Jr.") On 10/29/2010 7:47 PM, admin wrote: > WTF is T_PAAMAYIM_NEKUDOTAYIM? > > This has to be THE most asked question by new php developers when they come across it. > Can we please change the token name to T_DOUBLE_COLON so I don't have to hear about it > constantly? > > Those that disagree don't do enough PHP support to know how often it is asked. it's worth it. Is it that hard to at least review the mailing list archives before ranting? At least posters would sound like they have educated themselves on why what came to be, and argue sensibly for changes.