| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we have the following small example, we see that the word `subroutine` doesn't start in column 7 but in column 8.
```
subroutine expan()
c2345678 " " lb " " "
end
```
so the code is not converted from fixed form to free form Fortran and in the example (due to the odd number of double quoutes) result in:
```
********************************************************************
Error in file D:/speeltuin/bug_ftn_quote/small.f line: 5, state: 22(String)
********************************************************************
```
The condition regarding the column number was to restrictive.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
free issues
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Spelling corrections as found by codespell and in #561.
Some reported problems were already fixed, others are fixed here, with some exceptions (a,o.):
- "referenceby" in defgen.cpp as this is in the output and I cannot oversee the consequences (looks like none, but ...)
- "HANGEUL_CHARSET" left as is as in some MS documentation is written: 'HANGUL_CHARSET: Also spelled "Hangeul". Specifies the Hangul Korean character set.' (https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-wmf/0d0b32ac-a836-4bd2-a112-b6000a1b4fc9).
|
| |
|
| |
|
|\
| |
| | |
Fix typos
|
| |
| |
| |
| |
| |
| | |
Found via
```
codespell -q 3 -S *.js,*.po,./src/translator*,*.eps,./doc/changelog.doc -L ang,ans,attribs,ba,behaviour,classe,colour,german,iff,initialise,nam,nd,que,russian,statics,te,tim,uint
```
|
|/ |
|
| |
|
|
|
|
|
| |
Create a consistent way to display the state mnemonics of the different scanners (analogous to the fortranscanner.l)
Use an automatic procedure to generate the routine with the translation of the states to a string.
|
|\
| |
| | |
issue #7200 Fortran warning: type not declared or defined
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
problem in the statement:
```
type(log_handle_type), protected, save, &
bind(c, name="LOG_HANDLE_one") &
:: log_handle_one
```
is the fact that the "bind" attribute is not handled.
- added handling of the bind attribute
- extending the bind definition also with the single quote version.
|
|/
|
|
|
|
|
|
|
|
| |
In Fortran a file that is included is replaced by the doxygen preprocessor by something like:
`# 11 "<path>/<filename>" 2`
when this is in fixed form Fortran and the `<path>/<filename>` is long it is possible that the closing double quote is beyond position 72 and thus not seen resulting in:
```
Error in file <path>/<filename> line: 73, state: 22(String)
```
this is caused as the `#` is not handled properly in prepassFixedForm. The `#` should be handled analogous to e.g. `C`.
|
|\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
|
| |
| |
| |
| | |
Consistency
|
|/
|
|
| |
Signed-off-by: Adrian Negreanu <groleo@gmail.com>
|
|\
| |
| | |
Windows crash in case of incorrect end statement
|
| |
| |
| |
| | |
Some Fortran compilers accept the END statement instead of the mandatory END TYPE. The code crashes on Windows as no correct END statement is found.
|
|/ |
|
|\
| |
| | |
Continuation lines and labels
|
| |
| |
| |
| |
| | |
Better handling of continuation lines when converting from fixed form Fortran to free form Fortran, especially handling the information in columns 733 and further (which is in fixed formatted Fortran always comment)
An `end` statement can start not only on lines with spaces in front of it but also when a line has a label or the `end` can be after a `;`.
|
|/
|
|
| |
Create an easy possibility to show the Fortran source as converted from fixed form to free form.
|
| |
|
|
|
|
| |
The Fortran scanner can give a message when the scanner is aborted, in here there is also the state, but in the form of a number. This patch adds a little bit more descriptive text.
|
|
|
|
|
|
|
|
|
|
|
|
| |
In fixed formatted Fortran code the numbers in the first positions of the comment were filtered out.
This is a regression on pull request #655
example where the number '1' disappears:
!> \details
!> 1.) First point
subroutine tst
end subroutine
|
|
|
|
|
| |
The backslash (\) is in Fortran not an escape character but was handled as such, this has been corrected.
Handling of the different Fortran string types ('...' and "...") made more consistent.
|
|\
| |
| |
| | |
into albert-github-feature/bug_enum
|
| |
| |
| |
| | |
All ENUMs are anonymous as they don't have a name defined in the Fortran standard.
|
|\ \
| | |
| | | |
Fortran improvements
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- adding NON_RECURSIVE
- better handling of missing PROGRAM in case of following module / subroutine in same file
- ignore (numeric)-labels in fixed source form
- adding support for
- TYPE IS
- CLASS IS
- CLASS DEFAULT
|
|/
|
|
|
| |
- handling of type / class statement especially in declarations in source browser and scanner
- color code import statement in source browser
|
|
|
|
|
| |
Super trivial typos
Some are in qtools/ which I know is a 3rd party dependency but as we know is now obsolete upstream. I reckon it wouldn't be much of an issue to merge neverthless
Tacked on several more commits
|
|
|
|
| |
Corrected handling of (local) variables as functions as well as handling of non Fortran variables used in Fortran code.
|
| |
|
|
|
|
|
|
|
|
|
| |
- FORTRAN: comment in subroutine argument list
This patch fixes the problem that comment lines in continuation parts stopped the continuation part.
Patch consists of 2 parts:
- correct setting of continuation characters for fixed form source code
- ignoring lines with just comment (based on initial fix proposed by angus-g, but extended for empty lines and comment lines that contain a continuation character)
|
|
|
|
| |
improve performance
|
|\
| |
| | |
Bug 700381 - error state 21 with fortran code (fixed format)
|
| |
| |
| |
| | |
Problem is caused by similar quotes inside quotes, in Fortran it is possible to "escape" quotes by doubling them.
|
|/
|
|
|
| |
This patch fixes a problem on Linux where in a number of cases doxygen crashed when an unnamed interface existed and the routine itself was in the same source file.
Furthermore the end line of routines is set correctly so inline source code in Fortran will be possible as well.
|