James Kermode

Renaming the allocate and deallocate Fortran routines to `node_allocate` and `node_deallocate` respectively gets me a little further, as they are then recognised as the constructor and destructor for `t_node` objects...

Thanks for reporting. However, this is a huge amount of code. Please can you try to cut down to a minimal example which shows the problem? A single short fortran...

This just means the object files (plus possibly libraries as well) that contain your compiled code. It’s redundant with the `*.o` at the end, so I’ll clean this up and...

Ok, thanks for reporting. I’ll try to make a new release soon which should fix this issue.

I don't think there's a workaround for this problem at the moment. Perhaps we could add a `--keep` option to explicitly add some modules back in, or generalise `--only` to...

Closing in favour of #194

I'm afraid there's nothing simple to be done about this - this is what the Fortran representation of the string looks like. You can convert to a Python string with...

I'm afraid I didn't add support for objected-oriented Fortran and the `class` statement. Pull requests to improve this would be welcome!

Thanks for this contribution. The new examples seems very extensive; would it be possible to cut it down to something minimal which still demonstrates the problems with the previous implementation?

Still seems much larger than needed to test the changes you're proposing: please make a minimal example if at all possible, to speed up the evaluation of the test-set, e.g....