Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:70362 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72988 invoked from network); 24 Nov 2013 21:44:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Nov 2013 21:44:57 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.177 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.217.177 mail-lb0-f177.google.com Received: from [209.85.217.177] ([209.85.217.177:49424] helo=mail-lb0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CE/24-51929-75372925 for ; Sun, 24 Nov 2013 16:44:56 -0500 Received: by mail-lb0-f177.google.com with SMTP id w7so2530771lbi.36 for ; Sun, 24 Nov 2013 13:44:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XA8tM+A25AKCfsftNhBFJK+5JkrRCg3vkOgdIDJIDC8=; b=zWhX6LIk3qwQMNCZmKr88vlhwwyOv/E34xo/CSxvwILDptdqSabhiWU4crSjdJgImB rETQpMt0OvfeMKxvLy3PB2zqWvrsFaasPDZnXpbxmqL17mdcaaCF13Eod+gAKxvUeqN6 mP4BbC3RnSaRQ59sNng0y8uS3Gbd2B0lApo9L9VaNZMPjNFytAo70m4ivGvwmTfV6HdB NCmIdMrEO8mbsok6q/+R+SOQkW2nTBNJx9KVdRoyu7bh0jv5AGADEhtcLQQO6wX4W65V 57IzISyQXXh+oGSUoCQMR62a17Gqogi8mSQOvf4SRD188nFjV2m4Z/iioafMXDnkCa7U 1iwA== MIME-Version: 1.0 X-Received: by 10.153.7.106 with SMTP id db10mr12144244lad.9.1385329492800; Sun, 24 Nov 2013 13:44:52 -0800 (PST) Received: by 10.112.157.33 with HTTP; Sun, 24 Nov 2013 13:44:52 -0800 (PST) Received: by 10.112.157.33 with HTTP; Sun, 24 Nov 2013 13:44:52 -0800 (PST) In-Reply-To: <2CBED69B-2859-4F70-A56D-27281EBED4CE@newtekemail.com> References: <2CBED69B-2859-4F70-A56D-27281EBED4CE@newtekemail.com> Date: Sun, 24 Nov 2013 22:44:52 +0100 Message-ID: To: Robert Williams Cc: PHP internals , Tjerk Meesters , Chris London Content-Type: multipart/alternative; boundary=001a1134ba5650b9f204ebf32877 Subject: Re: [PHP-DEV] Re: rfc: pow-operator From: pierre.php@gmail.com (Pierre Joye) --001a1134ba5650b9f204ebf32877 Content-Type: text/plain; charset=UTF-8 On Nov 24, 2013 9:58 PM, "Robert Williams" wrote: > > > On Nov 24, 2013, at 8:57, "Pierre Joye" wrote: > > > > > it not be possible to do something similar than isset? Changing > > pow from a function to operator? The big advantage is that any > > existing code will benefit from it without code changes. > > As for existing code (and new code where people will inevitably use pow()), can the function call be optimized away? That is exactly what I asked. To make pow an operator, like isset, speed improvements will be the same than with using **. --001a1134ba5650b9f204ebf32877--