[
https://issues.apache.org/jira/browse/JEXL-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated JEXL-71:
------------------------------
Attachment: JEXL-71.patch
A fix for the 3 subtasks that involves a syntax change for Maps literal and
adds the Array literal + tests.
Will post separate patches for the "variables" subtask & Map/Integer soon.
> Parsing errors?
> ---------------
>
> Key: JEXL-71
> URL: https://issues.apache.org/jira/browse/JEXL-71
> Project: Commons JEXL
> Issue Type: Bug
> Reporter: Sebb
> Fix For: 2.0
>
> Attachments: JEXL-71.patch
>
>
> While testing with a basic command-line utility, I got the following odd
> behaviours:
> Note: input is denoted by >.
> ============
> > c.e
> 04-Aug-2009 23:25:46 org.apache.commons.jexl.Interpreter visit
> WARNING: org.apache.commons.jexl.scripting.main.m...@51![0,3]: 'c.e;'
> undefined variable e.e
> Return value: null
> > c
> Return value: {2=3, 4=5}
> > e
> Return value: 2
> The error message looks wrong - why is e.e mentioned? Surely it should be c.e?
> ===========
> > a=[1,2]
> Encountered " "," ", "" at line 1, column 5.
> Was expecting one of:
> ... etc.
> Same for
> > A=['b','c']
> However, I would expect this to work, as this is the syntax for an array as
> shown on the website.
> How does one create an array?
> =====
> > D=['a'=>'b']
> Return value: {a=b}
> > D['a']
> Return value: b
> This as expected. However, numbers behave rather oddly:
> > E=[1=>2]
> Return value: {1=2}
> > E[1]
> Return value: null
> > E['1']
> Return value: null
> There does not appear to be a way to access the value.
> Whereas, when using a string:
> F=['1'=>2]
> Return value: {1=2}
> F['1']
> Return value: 2
> F[1]
> Return value: 2
> In this case, both the string and the bare number are usable as the key.
> ====
> I can create test cases for these, but I'd like to confirm that these are
> bugs first
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
