Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77397
Return-Path: <leight@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 68581 invoked from network); 21 Sep 2014 00:16:34 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 21 Sep 2014 00:16:34 -0000
Authentication-Results: pb1.pair.com smtp.mail=leight@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=leight@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.182 as permitted sender)
X-PHP-List-Original-Sender: leight@gmail.com
X-Host-Fingerprint: 209.85.212.182 mail-wi0-f182.google.com  
Received: from [209.85.212.182] ([209.85.212.182:58524] helo=mail-wi0-f182.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id A8/22-55126-0E81E145 for <internals@lists.php.net>; Sat, 20 Sep 2014 20:16:33 -0400
Received: by mail-wi0-f182.google.com with SMTP id d1so1189323wiv.15
        for <internals@lists.php.net>; Sat, 20 Sep 2014 17:16:29 -0700 (PDT)
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=y/VtMYFSmiYyUN/MEaMK4m/g7bE+xqAKP+dOvOT4pao=;
        b=RCm8X6EfJrNluFeT5KSOx2axhakdEGj9w2k+PUV/hztNX9nazjJpBXug+BaJbVM7UR
         aMVkmSFbJsDT56j07tKtS1BLPvFEdQr0APw7hU2Ul+5xd+sfPGu2D2JQYhg1HTxSqxE3
         8CvF3AF74SMbcgaLV8V4yMb7/Xcz9zH1EdzYdwRnQv9NWHPpMjHk/BJp9nrIvdN/1TtJ
         44hLztIj223AQzxFUO4jmLgKgqK33rTMr/YeWs++Wr3Iw7J2GI7OomQVAVi2JeDZ1fuM
         PC+k3jcRmTJWR/nfpAxo5vk8/mnv8ZwH4a1hGwJfjamXl0Cs0JrHv5Mg+MzUaJtrkIqr
         e3hw==
MIME-Version: 1.0
X-Received: by 10.194.118.201 with SMTP id ko9mr10739065wjb.9.1411258589844;
 Sat, 20 Sep 2014 17:16:29 -0700 (PDT)
Received: by 10.217.55.195 with HTTP; Sat, 20 Sep 2014 17:16:29 -0700 (PDT)
In-Reply-To: <CAPwsocEEQEGpUs6yCJWa3q1TrjsNsEbpmtMt0OjuCXZSx72-Jw@mail.gmail.com>
References: <CAPwsocHm4wme7TDX-1hp=PdNGi0KzAwRz4RezW3KddV9_4m=JQ@mail.gmail.com>
	<1A5B2D07-FEC6-410E-85C9-3FBE2F105104@golemon.com>
	<CAPwsocEEQEGpUs6yCJWa3q1TrjsNsEbpmtMt0OjuCXZSx72-Jw@mail.gmail.com>
Date: Sun, 21 Sep 2014 01:16:29 +0100
Message-ID: <CAPwsocESQFtoJ6pmnyU823s4iAdCageZY4XmXcoZ5985-hnEwA@mail.gmail.com>
To: Sara Golemon <php@golemon.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Loop... or...
From: leight@gmail.com (Leigh)

On 20 September 2014 23:06, Leigh <leight@gmail.com> wrote:
>
> Lots to think about here, if it's at all viable this will need it's
> own separate RFC, it's a much more invasive change, but definitely a
> great idea.

NikiC and Bob have convinced me to carry on with the original
proposal, and bring up Saras ideas as another RFC afterwards, so the
full impact of converting loops to expressions can be judged on its
own merits. It is BC with this RFC, so no problem there.