Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with the BLOCK Statement #638

Closed
JulesKouatchou opened this issue Apr 1, 2024 · 1 comment · Fixed by #639
Closed

Issue with the BLOCK Statement #638

JulesKouatchou opened this issue Apr 1, 2024 · 1 comment · Fixed by #639

Comments

@JulesKouatchou
Copy link

Hi Peter,

I am trying to generate a documentation with Ford (7.0.3). Ford fails in files that have BLOCK/END BLOCK statements. When I comment out only the lines with BLOCK and END BLOCK, I do not have a problem.

Any pointer you provide will be appreciated. The link to the sample code is below.

Thank you for your assistance.

Cheers,

Jules


The code is in a tar.gzip file:

https://drive.google.com/file/d/1M2YzF8gj_XuttNdlPlWh9jl_Vo4s-0oR/view?usp=sharing

It has the following directory structure:

reproducer/
reproducer/docs/
reproducer/gFTL/
reproducer/gridcomps/
reproducer/include/

To run Ford, go to reproducer/docs/Ford/ and issue the command:

ford docs-with-remote-esmf.md

You will get the error message:

reproducer/gridcomps/cap3g/CapGridComp.F90
ERROR in file 'CapGridComp.F90': Unexpected variable in sourcefile 'CapGridComp.F90':
        type(PrivateWrapper) :: w
ERROR in file 'CapGridComp.F90': END statement outside of any nesting:
        end block
ERROR in file 'CapGridComp.F90': END statement outside of any nesting:
        end subroutine init
  Parsing files         ━━━━━━━━━━━━━━━━━━━━━━ 100% 2/2 0:00:00 0:00:00 ../../gridcomps/cap3g/CapGridComp.F90
Traceback (most recent call last):

The file reproducer/gridcomps/cap3g/CapGridComp.F90 relies on the include reproducer/include/MAPL_private_state.h where macros (having BLOCK/END BLOCK statements) are defined.

@ZedThree
Copy link
Member

ZedThree commented Apr 2, 2024

Thanks for the bug report and reproducer @JulesKouatchou! I have a fix for this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants