Extraneous brackets cause parsing for arithmetic operator error

[RaoulHC]

The following valid fortran fails to be parsed

      program main
      integer*4 bar
      call foo((bar)*2)
      end program main

Giving:

ProgramFilefortran-src: test.f, 3:22: test.f: parsing failed. 
Last parsed token: TStar (3:21)-(3:21).
CallStack (from HasCallStack):
  error, called at app/Main.hs:108:36 in main:Main

This seems to apply to all arithmetic operators (haven't tried other operators) and only if the brackets are on the left side.

[raehik]

Argh. This is surely caused by b335ac595b32fd784f2e9970325eb36bea44baa7 . I imagine it gets to the '(' VARIABLE ')' line in the CALLABLE_EXPRESSION rule:

https://github.com/camfort/fortran-src/blob/70c04566e72135cfefe37e75bc0ea8d587f333b7/src/Language/Fortran/Parser/Fixed/Fortran77.y#L750-L753

But (bar)*2 is an expression, not a variable. So it erroneously parses (bar), then has nowhere to go for the rest of the expression.

[raehik]

Works fine on commit 58b0de3d0612680b661fa3fddb24d7f044450cc1 (immediately before the arg expr change)

[RaoulHC]

Why exactly is that parsed differently? Is there anything significant about bracketed arguments?

[raehik]

In https://github.com/camfort/fortran-src/issues/203 we found some surprising cases where bracketing variables in call() argument lists produced different behaviour. We inserted an intermediate data type to enable disambiguating whether an arg was bracketed or not and adding parsing for it, above.

Not too sure how to approach this immediately. Do we have to refactor to handle bracketed expressions in a more complex way? may I ask @dorchard if he has any insights...?

[RaoulHC]

Oh I was unaware of that too, that's a feature that introduces some unfortunate syntactical ambiguity.

Not sure what the best way to handle that is. Obviously foo((var)*2) should still be valid so the parser might have some nastiness to deal with both these cases.