From issues-return-69014-archive-asf-public=cust-asf.ponee.io@commons.apache.org Mon Aug 6 10:59:06 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 5832F180789 for ; Mon, 6 Aug 2018 10:59:05 +0200 (CEST) Received: (qmail 2220 invoked by uid 500); 6 Aug 2018 08:59:04 -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 1985 invoked by uid 99); 6 Aug 2018 08:59:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Aug 2018 08:59:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id B2217C035B for ; Mon, 6 Aug 2018 08:59:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id bRzG5bqNTwsQ for ; Mon, 6 Aug 2018 08:59:03 +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 C22F65F2C3 for ; Mon, 6 Aug 2018 08:59:02 +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 436B0E2634 for ; Mon, 6 Aug 2018 08:59:02 +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 3512D23FAC for ; Mon, 6 Aug 2018 08:59:01 +0000 (UTC) Date: Mon, 6 Aug 2018 08:59:01 +0000 (UTC) From: "Dmitri Blinov (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (JEXL-264) Allow space, quote & double-quote in identifiers 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-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569893#comment-16569893 ] Dmitri Blinov edited comment on JEXL-264 at 8/6/18 8:58 AM: ------------------------------------------------------------ For this exact purpose I am using pseudo-variable "this" which is resolved to current context to allow script-writer to access context variables by using array syntax like this {code} this["My Variable"] {code} This is also useful when one wants to explicitly address context variable and avoid possible name clashing with any local variable. More relaxed syntax to name a variable is great but there ara other use-cases, like national character set names, names starting with digits etc which are prohibited by current syntax rules. Maybe we should have some unified solution for this? was (Author: dmitri_blinov): For this exact purpose I am using pseudo-variable "this" which is resolved to current context to allow script-writer to access context variables by using array syntax like this {code} this["My Variable"] {code} This is also useful when one wants to explicitly address context variable and avoid possible name clashing with any local variable > Allow space, quote & double-quote in identifiers > ------------------------------------------------ > > Key: JEXL-264 > URL: https://issues.apache.org/jira/browse/JEXL-264 > Project: Commons JEXL > Issue Type: Improvement > Affects Versions: 3.1 > Reporter: Henri Biestro > Assignee: Henri Biestro > Priority: Minor > Fix For: 3.2 > > > Since a Jexl context may be backed by a map that is not under Jexl's control, it may happen that keys in such a map contains spaces (quotes, backquotes). > Scripting these top-level variables is then not very easy; adding an escaping mechanism in the syntax for top-level identifiers is provably convenient in this case. > For example:In a script, {code}My\ Variable = 3{code} sets the top level variable keyed with the string "My Variable" with the value 3. -- This message was sent by Atlassian JIRA (v7.6.3#76005)