Better warning when in Fortran a comment block is not closed #10587
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When having e.g. a stray `@code` in the comment we get a warning like: ``` Error in file .../gmsh-4.12.2-source/api/gmsh.f90 line: 15475, state: 29(DocCopyBlock) ``` where the line 15475 is the end of the file. It is a bit hard to find where the problem actually occurs, so a warning like: ``` Error in file .../gmsh-4.12.2-source/api/gmsh.f90 line: 15475, state: 29(DocCopyBlock), starting command: '@code' probable line reference: 6689 ``` is better
|
albert-github
added a commit
to albert-github/doxygen
that referenced
this pull request
Jan 29, 2024
Analogues to doxygen#10587 we also need warnings for program units and as it can be nested we need a stack to record what is still open.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When having e.g. a stray
@codein the comment we get a warning like:where the line 15475 is the end of the file.
It is a bit hard to find where the problem actually occurs, so a warning like:
is better