Improved indexing

[btnlq]

• Support array element assignment
• Support indexing of multi-dimensional arrays
• Support indexer assignment

Partially resolve #39

[davideicardi]

Thanks @btnlq !
Why it is only partially solved? What is missing?

[btnlq]

Issue #39 describes three unrelated problems:

1. Variable assignment (GitHub_Issue_39_Simple_Reassignment from here)
2. Array element assignment (GitHub_Issue_39_Array_Reassignment)
3. Indexer assignment (GitHub_Issue_39_List_Reassignment)

This pull request solves the second problem. Later I will try to deal with the third problem.

[btnlq]

@davideicardi, done!

I fixed the third problem (support for indexer assignment). I also added support for multidimensional arrays.

[davideicardi]

Great pull request! Very good work.

Just a quick question, do you think that the AssignmentOperators is always respected also inside these new workflow? I think it is important for security reason. In some context you don't want to allow expressions that modify data ... Eventually we can ensure this by adding a specific unit test?

[btnlq]

AssignmentOperators is checked immediately when token '=' is detected. My changes did not break this behavior. But it’s impossible to prevent objects from being modified using methods like Dictionary.Add or List.Sort.

[davideicardi]

Just merged, v2.3.0 Thanks again!