Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:77433 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92379 invoked from network); 22 Sep 2014 07:49:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Sep 2014 07:49:38 -0000 Authentication-Results: pb1.pair.com smtp.mail=xinchen.h@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=laruence@php.net; sender-id=unknown Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.215.54 as permitted sender) X-PHP-List-Original-Sender: xinchen.h@zend.com X-Host-Fingerprint: 209.85.215.54 mail-la0-f54.google.com Received: from [209.85.215.54] ([209.85.215.54:51988] helo=mail-la0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 54/D3-08225-F84DF145 for ; Mon, 22 Sep 2014 03:49:36 -0400 Received: by mail-la0-f54.google.com with SMTP id ge10so6038611lab.41 for ; Mon, 22 Sep 2014 00:49:33 -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:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=2ahSMNRVkwqbSHz5u41dQOcjnoo8F1t681cVqlu8xuo=; b=S3B7weFfw+k2v3ZGs7Wb9ohV+bxbdQwLItxsO40dVpYZJXkKBVn/Ajo4NDJLV3KfME fCBSZk55hrqdswGInZ3su4gZNcHRBGoZLoT8giSPsbkcN59He+498/IBBjy3jmOySTHX yieU2I5hEVzkVlADrU7UDzj2vbW5u8NmljRsiaqxiGtSkv5DqchFRF2SzJPkRDqlBBwf 26g007EbPeqBVY7Y2DMUqLqu01VjvkTdAa4lU2/hmfvoD0+J+i2zW709UliPhphdpRbF xazF8YBX1ohs2K0SBOziY1pCg+jfoe0sk8Fv5JatsLfDs/Amc+SXTFz4yKnQbyWHrdGz eI5A== X-Gm-Message-State: ALoCoQlGQhSE2kYmI/NvYur44hVPXhh56gWQhzgFaI/E3Q3TaHp+hJapkV2sb0k/r+K3Dk1EJ7kKmhb36vgRbFiDT4Ik1WAh5RZNkWjSUQLB/vW9+sWXTU3cm86R6t7mZrnytcBTNqYFLt9npXZ/IRiiYXNKMSHfZg== X-Received: by 10.152.43.99 with SMTP id v3mr23880964lal.13.1411372173149; Mon, 22 Sep 2014 00:49:33 -0700 (PDT) Received: from mail-la0-f50.google.com (mail-la0-f50.google.com [209.85.215.50]) by mx.google.com with ESMTPSA id o4sm3467058lao.32.2014.09.22.00.49.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 22 Sep 2014 00:49:31 -0700 (PDT) Received: by mail-la0-f50.google.com with SMTP id ty20so6161598lab.37 for ; Mon, 22 Sep 2014 00:49:31 -0700 (PDT) X-Received: by 10.152.206.101 with SMTP id ln5mr23988385lac.46.1411372171434; Mon, 22 Sep 2014 00:49:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.187.234 with HTTP; Mon, 22 Sep 2014 00:49:11 -0700 (PDT) In-Reply-To: References: Date: Mon, 22 Sep 2014 15:49:11 +0800 Message-ID: To: Leigh Cc: PHP Internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC] Loop... or... From: laruence@php.net (Xinchen Hui) Hey: On Sat, Sep 20, 2014 at 5:56 AM, Leigh wrote: > Hello list! > > This is an item that has been repeatedly requested in various forms, > with no solid implementation to back it up, yet remaining quite > desirable to the developer community at large. > > Loops with a default block, executed in the event that the loop is > never entered. > > https://wiki.php.net/rfc/loop_or > > Traditionally this is requested as a loop {} else {} structure, > however due to the choice of keyword this causes significant BC > problems. > > I have written an RFC presenting this feature as loop {} or {} along > with how I intend to implement it. I have consulted with several core > contributors as well as normal developers, and this seems to be the > most BC-complete option. > > A poll of local developers indicates a strong positive response > supporting this feature, so please take the time to consider and > discuss what is laid out in the RFC, as many of us would like this to > become a permanent fixture of the language. > > I especially need input regarding Opcache concerns, as this is not an > area of expertise for me. > > I will be developing the patch myself, and hope to have a full proof > of concept completed by the end of this weekend. (for and while are > both working, foreach currently segfaults, I am working on it) > > Thanks for reading. > > Leigh. Maybe I am too conservative. I don't like this idea......... :< And I DO THINK, we should try to stop brings lots of new things into PHP7. I am worring whether it can be release in the next year.... thanks > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > -- Xinchen Hui @Laruence http://www.laruence.com/