Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68249 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24321 invoked from network); 20 Jul 2013 04:28:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Jul 2013 04:28:10 -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 203.88.119.10 cause and error) X-PHP-List-Original-Sender: lists@rotorised.com X-Host-Fingerprint: 203.88.119.10 mta10-d1.ip1.cbr1.mail-filtering.com.au Received: from [203.88.119.10] ([203.88.119.10:30465] helo=mta10-d1.ip1.cbr1.mail-filtering.com.au) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BC/2C-13120-7D11AE15 for ; Sat, 20 Jul 2013 00:28:09 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhgFALMQ6lGva64TjGdsb2JhbABbgzsBrVWTSoERFg4BAQEnPIIkAQEFeBELDQsJFg8JAwIBAgFFEwgBAYgLt0mQFhaDaAOZBoRnNo4r X-IPAS-Result: AhgFALMQ6lGva64TjGdsb2JhbABbgzsBrVWTSoERFg4BAQEnPIIkAQEFeBELDQsJFg8JAwIBAgFFEwgBAYgLt0mQFhaDaAOZBoRnNo4r X-IronPort-AV: E=Sophos;i="4.89,706,1367935200"; d="scan'208";a="800302821" 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; 20 Jul 2013 14:28:04 +1000 Received: from 217.33.96.58.static.exetel.com.au ([58.96.33.217]:52541 helo=[192.168.1.134]) by ub005lcs09.cbr.the-server.net.au with esmtpa (Exim 4.80.1) (envelope-from ) id 1V0Om4-003MCM-2p for internals@lists.php.net; Sat, 20 Jul 2013 14:28:04 +1000 Message-ID: <51EA11E2.7030807@rotorised.com> Date: Sat, 20 Jul 2013 14:28:18 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: internals@lists.php.net References: <1374256806.3946.101.camel@guybrush> <51EA0F30.3010609@rotorised.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Language constructs and callability From: lists@rotorised.com (Ryan McCue) Sara Golemon wrote: > Well, now... to be fair... You could make them functions and use the same > parser trick the backtick operator uses. to map the non-parenthesized > versions.... feels messy though. I'd just hate to get stuck with a hacky > workaround like that for the long term. That's what I meant by the "backwards compatibility layer". Not saying we have to deprecate the use as a construct, but why can't we enable the use as a function (and hence, callback, etc)? It feels less cleaner from my point of view (userland). -- Ryan McCue