From issues-return-69156-archive-asf-public=cust-asf.ponee.io@commons.apache.org Tue Aug 14 16:29:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 8023118067A for ; Tue, 14 Aug 2018 16:29:03 +0200 (CEST) Received: (qmail 14124 invoked by uid 500); 14 Aug 2018 14:29:02 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 14113 invoked by uid 99); 14 Aug 2018 14:29:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Aug 2018 14:29:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 13E631A1D5B for ; Tue, 14 Aug 2018 14:29:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id wRPFWU1zWQTR for ; Tue, 14 Aug 2018 14:29:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 130FB5F3BD for ; Tue, 14 Aug 2018 14:29:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 9A872E0E1D for ; Tue, 14 Aug 2018 14:29:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4CBD223F9E for ; Tue, 14 Aug 2018 14:29:00 +0000 (UTC) Date: Tue, 14 Aug 2018 14:29:00 +0000 (UTC) From: "Henri Biestro (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (JEXL-266) Allow to remove an element from iterator collection within for-loops MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/JEXL-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16579881#comment-16579881 ] Henri Biestro commented on JEXL-266: ------------------------------------ I'm afraid this is adding a new keyword and modifying the syntax for a very specific need... What about trying to expose the iterator and/or the variable through an API to allow a more generic 'remove(item)' that could be resolved as a method in the context or arithmetic with a (tbd) signature ? > Allow to remove an element from iterator collection within for-loops > -------------------------------------------------------------------- > > Key: JEXL-266 > URL: https://issues.apache.org/jira/browse/JEXL-266 > Project: Commons JEXL > Issue Type: New Feature > Affects Versions: 3.1 > Environment: I have created a patch as initial implementation for this new feature, please see github pull request here [pr#5|https://github.com/apache/commons-jexl/pull/5]. I whould be very grateful if this could be interesting for the community and included in master branch. Thanks in advance! > Reporter: Dmitri Blinov > Priority: Minor > > The for-loop in JEXL provides a convenient way to iterate over different types of collections, however, its not possible for a script writer to utilize underlying > {code:java} > iterator.remove(){code} > method within such a loop. The proposal is to introduce new {{remove}} statement which should be used within for-loops and should internally call {{iterator.remove()}} method and skip the loop to the next element; > For example, the following code should remove items {{1,2,3}} from set and return value {{3}}. > {code:java} > var set = {1,2,3,4,5,6}; for (var item : set) if (item <= 3) remove; return size(set) > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)