commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Biestro (JIRA)" <>
Subject [jira] Issue Comment Edited: (JEXL-73) Undefined variables not reported correctly
Date Wed, 05 Aug 2009 13:44:14 GMT


Henri Biestro edited comment on JEXL-73 at 8/5/09 6:43 AM:

Interpreter.visit for Reference (and sibling for Assignment) does not use the proper nodes
when looping to build the variable name.

      was (Author: henrib):
    Roots in Interpreter.getAttribute that wrongly converts the attribute to a String before
the call to the Uberspect.getPropertyGet.
This issue as a sibling with Interpreter.setAttribute that wrongly does the same.
> Undefined variables not reported correctly
> ------------------------------------------
>                 Key: JEXL-73
>                 URL:
>             Project: Commons JEXL
>          Issue Type: Sub-task
>            Reporter: Henri Biestro
>             Fix For: 2.0
> Trying to eval('c.e') with 'c' existing but no 'e' property wrongly report 'e.e' as the
undefined variable.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message