Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:49982 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72250 invoked from network); 30 Oct 2010 01:24:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Oct 2010 01:24:43 -0000 Authentication-Results: pb1.pair.com smtp.mail=scott@macvicar.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=scott@macvicar.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain macvicar.net from 97.107.131.220 cause and error) X-PHP-List-Original-Sender: scott@macvicar.net X-Host-Fingerprint: 97.107.131.220 whisky.macvicar.net Linux 2.6 Received: from [97.107.131.220] ([97.107.131.220:52285] helo=whisky.macvicar.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F2/60-04551-AD37BCC4 for ; Fri, 29 Oct 2010 21:24:43 -0400 Received: from [172.16.1.3] (76-217-210-0.lightspeed.sntcca.sbcglobal.net [76.217.210.0]) by whisky.macvicar.net (Postfix) with ESMTP id E984A468CC; Fri, 29 Oct 2010 21:24:39 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii In-Reply-To: <4CCB7247.7020408@codeangel.org> Date: Fri, 29 Oct 2010 18:24:38 -0700 Cc: internals@lists.php.net Content-Transfer-Encoding: quoted-printable Message-ID: <57DF12F0-6BFD-4058-B854-6710457AF692@macvicar.net> References: <4CCB6B21.1070708@codeangel.org> <4CCB70CE.90901@rowe-clan.net> <4CCB7247.7020408@codeangel.org> To: admin X-Mailer: Apple Mail (2.1081) Subject: Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON From: scott@macvicar.net (Scott MacVicar) On Oct 29, 2010, at 6:17 PM, admin wrote: > On 10/29/2010 08:11 PM, William A. Rowe Jr. wrote: >> On 10/29/2010 7:47 PM, admin wrote: >> =20 >>> WTF is T_PAAMAYIM_NEKUDOTAYIM? >>>=20 >>> 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? >>>=20 >>> Those that disagree don't do enough PHP support to know how often it = is asked. it's worth it. >>> =20 >> Is it that hard to at least review the mailing list archives before = ranting? >>=20 >> At least posters would sound like they have educated themselves on = why what >> came to be, and argue sensibly for changes. >>=20 >> =20 > obviously the old arguments didn't work, time to start anew. >=20 using a name like "admin" in your email headers isn't going to be very = receptive. For what its worth its Hebrew for double colon. I'm all for the change, = will see what I can do next week. - S