partial implementation of object field access leaves valid method invocations on non-primary expressions marked as ERROR

[janw4ld]

This issue is marginally related to parenthesized_expressions, the grammar you've defined separates expression kinds into

• _prefix_expression which are expressions with fields accessible by . on them, and
• _expression which are the general / complex expression that evaluate to simpler values

and defines a dotted_identifier lexeme that consists of _prefix_expression followed by '.' then identifier.

Note

the distinction between simple and complex expressions is more formally known as "expressions" for the general case vs "primary expressions" for the grammar's atoms

this definition results in the following parser shortcomings

• field access on complex expressions parsing as an ERROR despite being valid groovy code
  

• no support for parsing field access with a runtime evaluated string subscript -only identifier, so although the code below is a valid groovy expr that subscripts the range 1..3 with each normally, after i've implemented field access on general _expressions, the code is parsed as a function call with a null identifier and ("ea"+"ch") as its argument list.