Konrad
@certik Thanks, I'll fix this today / tomorrow in total.
Somehow the scopes get renamed; I haven't figured out what change caused this to happen. Will debug in more detail.
Missing setting up the function call args when encountering `FuncCallOrArray`; after that it should finally be done.
I've put in a lot of edge cases that `EXTERNAL` needs to keep track of; also some comments into the (for now single) integration test what needs to be achieved...
`scipy/optimize/minpack/hybrd.f` has the procedure declaration + concerning `external` -> somehow we need to be able to pass functions / outer dependencies like gfortran does. ```fortran ... subroutine hybrd(fcn,n ... external...
Re above comment and: `scipy/optimize/minpack/hybrd.f` I'm inspecting the `--allow-implicit-interface` flag -- no type checking is enabled, a function call can be ran from a `Variable_t`. I think this won't work...
@certik I suggest merging this (after you've reviewed the changes) and I occupy myself in a next (or several next) PR(s) to enable functions as arguments and type checking for...
@certik Sure. As I've mentioned, my changes highlight that there is something deeper to be fixed. That is, type checking and implicit function declaration. It'd be great to meet to...
With the linked merged PR, can this be considered done and we can implement the visitors in LFortran?
How can this add support for `complex(16)` if double precision complex isn't supported yet?