| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
This was found while testing with Clang's -Wdocumentation
-Wdocumentation-pedantic options.
Note from the coding style used it would seem useDict would be the more
appropriate name, but usedict is used on multiple occasions in this file.
|
|
|
|
|
|
| |
- moved unescapeCharsInString to util.cpp
- restructured flow keyword counting
- make flow keyword counting work for python and fortran code as well
|
|
|
|
| |
Consistency
|
| |
|
|
|
|
|
| |
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 `;`.
|
| |
|
|
|
|
| |
The tooltips (XHTML) should not be displayed per code fragment but for the entire (output) file as otherwise tooltips might be added multiple times resulting in double IDs.
|
|
|
|
|
| |
When functions are used they have to be declared and were seen as local variables even when the 'external' keyword had been applied.
Functions are now not seen anymore as local variables as soon as the 'external' keyword has been applied.
|
| |
|
|
|
|
|
| |
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.
|
|\ \
| | |
| | | |
Misc. typos
|
| | |
| | |
| | |
| | | |
Found via `codespell`
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
REAL can have multiple meanings in Fortran:
- data type
- name of (conversion) function
in case of free formatted code the word "real" cab appear at the beginning of a (physical) line and would be interpreted incorrectly.
Fortran comment lines always end at the end of the line (no block comments) so the code coloring of comment lines should always be terminated.
|
|\ \
| | |
| | | |
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
|
|
|
|
| |
The comma was colored as part of the word only (keywordtype), this should not be the case.
|
|
|
|
| |
Corrected handling of (local) variables as functions as well as handling of non Fortran variables used in Fortran code.
|
| |
|
|
|
|
|
|
|
|
|
| |
This patch makes the handling of the \snippet and other commands consistent between the different languages (no line numbers anymore with python) and also introduces analogous to \includelineno the command \snippetlineno.
Some non relevant changes:
- *code.l Calculation of the end line was incorrect, in case of a snippet the end line was the number of lines of the snippet and not reltive to the start line.
- *code.l made consistent over the different laguages, enabling exBlock and inlineFragment
- testing/indexpage.xml in test 14 the \snippet command was used with python and giving line numbers, linenumbers are now gone (consistency)
|
|\
| |
| |
| |
| | |
albert-github/feature/bug_code_keyword_operator_assignment
Color code word OPERATOR and ASSIGNMENT as keyword in FORTRAN code
|
| | |
|
|/ |
|
| |
|
|
|
|
| |
improve performance
|
| |
|
|
|
|
|
|
| |
The version checks only considered YY_FLEX_SUBMINOR_VERSION and did not
take YY_FLEX_MINOR_VERSION into account, which made them fail with
flex-2.6.0.
|
|
|
|
| |
When using e.g. IMPLICIT INTEGER only the IMPLICIT was seen as keyword and INTEGER was not seen as keyword. Now types are seen as keywords as well.
|
|
|
|
| |
Signed-off-by: Adrian Negreanu <adrian.m.negreanu@intel.com>
|
|
|
|
| |
According to the Fortran standard position 73 and further on a line are comment. Until now this was not considered.
|
| |
|
| |
|
|\
| |
| | |
Convert FORTRAN modules to namespaces
|
| | |
|
| | |
|
| |
| |
| |
| | |
This helps fix linking issues and ambiguity related to the difference between classes and modules in FORTRAN 2003+.
|
|\ \
| | |
| | | |
Fortran color CALL as keyword
|
| | |
| | |
| | |
| | | |
Color the word CALL as keyword.
|
|/ /
| |
| |
| |
| |
| |
| | |
This is a regression on pull request 259.
Fortran code like:
end if
was not colored properly anymore. This has been corrected with this patch.
|
|\ \
| | |
| | |
| | |
| | | |
albert-github/feature/bug_fortran_source_continuation
Fortran continuation character seen as begin of function call
|
| |/
| |
| |
| |
| | |
In case in fixed format code a line like:
" x ( " existed and the x was on position 6 the "x (" was seen as the start of a function call.
|
|/
|
|
| |
The color for the single END in Fortran code was of the color of the flow type entities though for all the flow entities the entity name is mandatory. For the entity statements of some keywords e.g. SUBROUTINE and FUNCTION the entity name is not mandatory with the END statement. The color of the single END statement has been changed from the flow type to the normal keyword type.
|
|\
| |
| | |
Last comment of \code{.f90} missing
|
| |
| |
| |
| |
| |
| |
| | |
In case e.g. an number of Fortran variables are documented as an example in a \code block and the last line looks like:
INTEGER :: var !< documentation
The "!< documentation" is missing as the last block was not rendered.
Note: STRIP_CODE_COMMENTS has to be NO as otherwise the code comment will anyway, correctly, be absent.
|