Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68252 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30798 invoked from network); 20 Jul 2013 04:47:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Jul 2013 04:47:03 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@golemon.com; spf=softfail; sender-id=softfail Authentication-Results: pb1.pair.com header.from=php@golemon.com; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.220.45 as permitted sender) X-PHP-List-Original-Sender: php@golemon.com X-Host-Fingerprint: 209.85.220.45 mail-pa0-f45.google.com Received: from [209.85.220.45] ([209.85.220.45:51509] helo=mail-pa0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 78/AD-13120-7461AE15 for ; Sat, 20 Jul 2013 00:47:03 -0400 Received: by mail-pa0-f45.google.com with SMTP id bg2so1538758pad.32 for ; Fri, 19 Jul 2013 21:46:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=4jCptrQ8Jw6b3Hs9gZMm+arpBK26tJHjQDy9GgShz18=; b=cvXxW9aYAlLrk1errAV8nKN1hxlOd8tPuBnlE5hFAxfWUOhVJrImf3+QnfahByolT0 stpvyuEtervGKkqEZPn1vsl/MEsRBd990HrwG2U8mfJwpXYRU+Fjn9SHeUYRH89T692P joVHBLt/6Vp+LWGBckWZ76MyQIi3xfzn+F0dfH6I4TC5BdXP2AgIK0cImc4YVOOX6EKQ dUa7fVx+iGtNuoRMGHbMBnBxjZRQ9OVjYxwxBYFY+SCM+k4rsZXkkrjpq7y1IETnJhXk 1s2z7u1AdAIKqf15VvdPxKt00n6AkUekdafJ9HhidTMtV1X0v0l14XoJwiV+kvcfRvQ2 wu0Q== MIME-Version: 1.0 X-Received: by 10.68.173.97 with SMTP id bj1mr20551533pbc.176.1374295619444; Fri, 19 Jul 2013 21:46:59 -0700 (PDT) Sender: php@golemon.com Received: by 10.70.128.71 with HTTP; Fri, 19 Jul 2013 21:46:59 -0700 (PDT) X-Originating-IP: [98.210.180.187] In-Reply-To: <51EA11E2.7030807@rotorised.com> References: <1374256806.3946.101.camel@guybrush> <51EA0F30.3010609@rotorised.com> <51EA11E2.7030807@rotorised.com> Date: Fri, 19 Jul 2013 21:46:59 -0700 X-Google-Sender-Auth: nwRFpxxhzGZ5oOTL5_Qp5qMQj4A Message-ID: To: Ryan McCue Cc: PHP internals Content-Type: multipart/alternative; boundary=047d7b339f1736a81f04e1ea229d X-Gm-Message-State: ALoCoQk4b9kAmnOhTwDlBnrdrZc706KsJ/wCzVh60v/h/Mm0WCMc+Hg6aLCjD2hJhOJrBt/NKOQa Subject: Re: [PHP-DEV] Language constructs and callability From: pollita@php.net (Sara Golemon) --047d7b339f1736a81f04e1ea229d Content-Type: text/plain; charset=ISO-8859-1 The danger I see there is the fact that we'd have two different implementations of the same functionality (leading to potential code-rot), and worse, it wouldn't be obvious from userspace when one implementation would be used over the other. (We'd know, but I mean for the average PHP user, leading to weird unreproducible bug reports). -Sara On Fri, Jul 19, 2013 at 9:28 PM, Ryan McCue wrote: > 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 > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --047d7b339f1736a81f04e1ea229d--