Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69081 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 5656 invoked from network); 12 Sep 2013 07:09:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Sep 2013 07:09:05 -0000 Authentication-Results: pb1.pair.com smtp.mail=lists@rotorised.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lists@rotorised.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain rotorised.com from 117.55.227.19 cause and error) X-PHP-List-Original-Sender: lists@rotorised.com X-Host-Fingerprint: 117.55.227.19 mta19-d1.ip1.cbr1.mail-filtering.com.au Received: from [117.55.227.19] ([117.55.227.19:63537] helo=mta19-d1.ip1.cbr1.mail-filtering.com.au) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DE/94-12981-E8861325 for ; Thu, 12 Sep 2013 03:09:03 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArMAALhnMVKva64Tl2dsb2JhbABbgz+9bIMlgSMWDgEBAQEBCBYHPIIlAQEFgQkLDQsJJQ8CRhMIAQGHfb1Xj3IWhAcDmSiEbDuOUA X-IPAS-Result: ArMAALhnMVKva64Tl2dsb2JhbABbgz+9bIMlgSMWDgEBAQEBCBYHPIIlAQEFgQkLDQsJJQ8CRhMIAQGHfb1Xj3IWhAcDmSiEbDuOUA X-IronPort-AV: E=Sophos;i="4.90,889,1371045600"; d="scan'208";a="834000145" Received: from unknown (HELO ub005lcs09.cbr.the-server.net.au) ([175.107.174.19]) by smtp-data2.ironport1.cbr1.mail-filtering.com.au with ESMTP; 12 Sep 2013 17:08:59 +1000 Received: from 217.33.96.58.static.exetel.com.au ([58.96.33.217]:60394 helo=[192.168.1.134]) by ub005lcs09.cbr.the-server.net.au with esmtpa (Exim 4.80.1) (envelope-from ) id 1VK11N-000mHQ-S5 for internals@lists.php.net; Thu, 12 Sep 2013 17:08:57 +1000 Message-ID: <52316891.90802@rotorised.com> Date: Thu, 12 Sep 2013 17:09:05 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Support for keywords where possible From: lists@rotorised.com (Ryan McCue) Bob Weinand wrote: > I tried to widen the naming possibilities by allowing to use keywords as identifiers (for function names, class names, label (goto) names, ...) where possible. It doesn't break any BC. Is the token still T_LIST/T_DEFAULT given that example above, or would those be T_STRINGs now? I can think of a bunch of userland stuff (basically every documentation generator) that will break if the class/function name is not a T_STRING. That said, +1 for the feature, great idea. -- Ryan McCue