Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:77400 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72302 invoked from network); 21 Sep 2014 00:23:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Sep 2014 00:23:28 -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.192.176 as permitted sender) X-PHP-List-Original-Sender: php@golemon.com X-Host-Fingerprint: 209.85.192.176 mail-pd0-f176.google.com Received: from [209.85.192.176] ([209.85.192.176:61910] helo=mail-pd0-f176.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6D/F2-55126-F7A1E145 for ; Sat, 20 Sep 2014 20:23:27 -0400 Received: by mail-pd0-f176.google.com with SMTP id z10so885733pdj.7 for ; Sat, 20 Sep 2014 17:23:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=CrQSsmWLaOg2asZ/f8g8P7l0Fjvv8DZw72y59yFV9eY=; b=Q68MzhW2dwCmZGmcsJdMbgEjEu65PO/12v7K7Hco0vIOQEcOItuiYGUyTQ22BpR27k Lf8elZC7i+5xXxUCBlRFqrwA5eXjKh3RkK7YkCGqlTVWpjtnGusIowETsZp49Sw5pSBP b5N1fVBLuqte3/tVgUW1BY8BaelA20ejFotyX+NzZRZM543eu0yihr+8lFSbwpwvvR9i mtAKtlLdgkgZWYckLkr4cwk2kHgNsY2nycjCWpFDz+0HSbt28NcfJ9Ixvjb8yOQ+Lv2H MPhZKwm97lJ78+A2KJ2fkLTD8NemOR6j6LL2iSOmuXnv1235mZf/76g0tZ8Ixf1qy+Bg MVmw== X-Gm-Message-State: ALoCoQneb4j1a83QfOuuHVBuPuTP/rMm+QpBVWsOcm8r360zyOPLgqmvqaBKeThby3UI/xJZAx5d MIME-Version: 1.0 X-Received: by 10.68.57.142 with SMTP id i14mr11940435pbq.64.1411259004632; Sat, 20 Sep 2014 17:23:24 -0700 (PDT) Sender: php@golemon.com Received: by 10.70.100.67 with HTTP; Sat, 20 Sep 2014 17:23:24 -0700 (PDT) X-Originating-IP: [173.252.71.189] In-Reply-To: References: <1A5B2D07-FEC6-410E-85C9-3FBE2F105104@golemon.com> Date: Sat, 20 Sep 2014 17:23:24 -0700 X-Google-Sender-Auth: jTYHv-OUgqGa97zSKt8z7iKkQDY Message-ID: To: Leigh Cc: "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC] Loop... or... From: pollita@php.net (Sara Golemon) On Sat, Sep 20, 2014 at 5:16 PM, Leigh wrote: > On 20 September 2014 23:06, Leigh 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. > Agreed. If we do find a nice way to make loops into expressions and make default blocks work with that, then the explicit LOOP/OR syntax can vanish and work implicitly with the expression approach. -Sara