groovy

Evaluation fails after the first subscript operator

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0-beta-2
  • Fix Version/s: 1.0-beta-3
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

After a subscript operator is encountered, expression evaluation seems to stop.

For example, if we have the following map:

a = ['out1':['in1':1, 'in2':2], 'out2':3]

The following expression evaluates correctly to 1:
a.out1.in1

This expression evaluates to null:
a['out1'].in1

And this evaluates to ["in1"]:
a['out1']['in1']

The same thing happens when using the subscript operator on a List of Java objects; the expression fails to evaluate correctly after the first subscript operator is encountered.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Rod Cope added a comment -

This problem also affects slicing. For example, currently the following cannot be done:

a = [1,2,3,4,5]
a[2..3].each

{ println( it ) }
Show
Rod Cope added a comment - This problem also affects slicing. For example, currently the following cannot be done: a = [1,2,3,4,5] a [2..3] .each { println( it ) }
Hide
Permalink
james strachan added a comment -

Now fixed - there were various bugs here where stuff after [] was ignored, should now work.

Show
james strachan added a comment - Now fixed - there were various bugs here where stuff after [] was ignored, should now work.
Hide
Permalink
james strachan added a comment -

don't know why you can't edit closed issues

Show
james strachan added a comment - don't know why you can't edit closed issues

People

  • Assignee:
    Unassigned
    Reporter:
    Rod Cope
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: