summaryrefslogtreecommitdiffstats
path: root/src/fortrancode.h
Commit message (Collapse)AuthorAgeFilesLines
* Refactoring: remove implicit conversion from QCString to const char *Dimitri van Heesch2021-04-221-2/+2
| | | | | | | | | | | | | | | | | This commit changes the following in relation to string use - The implicit convert from 'QCString' to 'const char *' is removed - Strings parameters use 'const QCString &' as much as possible in favor over 'const char *' - 'if (s)' where s is a QCString has been replaced by 'if(!s.isEmpty())' - data() now always returns a valid C-string and not a 0-pointer. - when passing a string 's' to printf and related functions 'qPrint(s)' is used instead of 's.data()' - for empty string arguments 'QCString()' is used instead of '0' - The copy() operation has been removed - Where possible 'qstrcmp(a,b)==0' has been replaces by 'a==b' and 'qstrcmp(a,b)<0' has been replaced by 'a<b' - Parameters of string type that were default initialized with '= 0' are no initialized with '= QCString()'
* Refactoring: making fortrancode.l reentrantDimitri van Heesch2020-09-101-8/+7
|
* Cleanup unused/unwanted parser dependencies on code generatorDimitri van Heesch2020-01-261-1/+0
|
* Split language parser into "outline parser" and "code parser"Dimitri van Heesch2019-12-031-7/+39
|
* Improved const correctness and added support for inline namespacesDimitri van Heesch2019-04-211-1/+1
|
* Bump copyright yearDimitri van Heesch2015-02-261-1/+1
|
* Fortran: fixed format position 73 and further is commentalbert-github2015-01-041-0/+1
| | | | According to the Fortran standard position 73 and further on a line are comment. Until now this was not considered.
* Some restructuring and some compiler warning fixesDimitri van Heesch2014-03-151-3/+5
|
* Bug 625601 - FORTRAN: recognition free versus fixed formatted codealbert-github2014-03-091-1/+1
| | | | | The recognition of the type (free or fixed) of Fortran code is not reliable possible. A well known possibility as used with compilers as well is to specify the type of code by means of the extension. With EXTENSION_MAPPING it is possible to select the type of Fortran code, when not explicitly set doxygen tries to guess the type of Fortran code.
* Updated copyrightDimitri van Heesch2014-02-111-1/+1
|
* Bug 707641 - `FILTER_SOURCE_FILES=YES` required to build CALL_GRAPHSSergio Oller2013-09-281-1/+2
| | | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=707641 Add references if the file is filtered, as the parser does not know whether we are insideBody or not.
* Release-1.8.3.1-20130324Dimitri van Heesch2013-03-241-0/+2
|
* Release-1.8.3.1Dimitri van Heesch2013-01-201-1/+1
|
* Release-1.8.2-20121118Dimitri van Heesch2012-11-181-3/+0
|
* Release-1.8.2Dimitri van Heesch2012-08-111-3/+3
|
* Release-1.7.6.1-20120220Dimitri van Heesch2012-02-201-1/+1
|
* Release-1.7.3-20110123Dimitri van Heesch2011-01-231-1/+1
|
* Release-1.6.3-20100324Dimitri van Heesch2010-03-241-1/+1
|
* Release-1.6.2-20100124Dimitri van Heesch2010-01-241-1/+1
|
* Release-1.5.4-20080101Dimitri van Heesch2008-01-171-1/+1
|
* Release-1.5.3-20070815Dimitri van Heesch2007-08-151-0/+35