Created by James Hurrell, last modified on Jul 31, 2020
This documentation is not maintained. Please refer to doc.castsoftware.com/technologies to find the latest updates.

  • 1.1.1-funcrel
  • 1.1.0-funcrel

    • 1.1.4-funcrel

    Resolved Issues

    Customer Ticket IdDetails
    27872Rule Rationale update for the QR (rule id - 1002208): "All Read and Write statements in Programs must use the return code IOSTAT (FORTRAN)"

    Other Updates

    Details
    After upgrade "Add Version" would not throw error " Dependency dmtcoetechnoua:2.0 is missing: library dmtcoediscovererfortran"
    Fortran Analyzer no longer supports Oracle or SQL server as storage service.

    Rules

    Rule IdNew RuleDetails
    1002088FALSEWeight for "Avoid too many Statements (STMT) in a Subroutine (FORTRAN)" has been changed from 0 to 1
    1002090FALSEWeight for "Avoid too many Statements (STMT) in a Program (FORTRAN)" has been changed from 0 to 1
    1002092FALSEWeight for "Avoid too many Statements (STMT) in a Function (FORTRAN)" has been changed from 0 to 1
    1002094FALSEWeight for "Avoid too many Statements (STMT) in a Module (FORTRAN)" has been changed from 0 to 1
    1002110FALSEWeight for "Avoid Programs with High Average size of Statements (AVGS) (FORTRAN)" has been changed from 0 to 1
    1002112FALSEWeight for "Avoid Subroutines with High Average size of Statements (AVGS) (FORTRAN)" has been changed from 0 to 1
    1002114FALSEWeight for "Avoid Functions with High Average size of Statements (AVGS) (FORTRAN)" has been changed from 0 to 1
    1002116FALSEWeight for "Avoid Modules with High Average size of Statements (AVGS) (FORTRAN)" has been changed from 0 to 1

    1.1.3-funcrel

    Resolved Issues

    Customer Ticket IdDetails
    25153Avoid untested Return Code variables after ALLOCATE in Programs (FORTRAN) - returns false positive when no ALLOCATE is present in the code
    25225Missing security violations for “Avoid untested Return Code variables after Read or Write in Subroutines (FORTRAN)”.
    25487Fortran function objects are not always created in Metamodel
    24044Rule 1002142 -Unavoid un-deallocated variables or arrays in Fortran-90 Modules (FORTRAN) -description needs update
    25198Associated Value details should be clear for a violation - Fortran

    1.1.2-funcrel

    Resolved Issues

    Customer Ticket IdDetails
    23872Fortran Analyzer 1.1.1-funcrel creates over 500 false positives for rule Avoid Untested Return Code variables after ALLOCATE in Subroutines

    Other Updates

    Details
    Incorrect objects created for Fortran Stat Variable

    1.1.1-funcrel

    Updates

    Rename "Extension" to Fortran "Analyzer"

    Fortran Extension is now known as Fortran Analyzer.

    Deprecate FortranIfConstruct, FortranSelectCase, FortranDoConstruct

    Objects of type FortranIfConstruct, FortranSelectCase, FortranDoConstruct will no longer be created after analysis. Links and metrics belonging to these objects will now belong to their respective container artifacts. Therefore, after upgrade, QR results will change.

    Resolved Issues

    The following table lists the bugs fixed in Fortran 1.1.1-funcrel.

    Internal IDDescriptionImpact?
    FORTRAN-34Getting many more FORTRAN warnings and not getting any violation in dashboardThe warnings for types FortranIfConstruct, FortranSelectCase, FortranDoConstruct have been removed as these objects are no longer created.

    1.1.0-funcrel

    What to expect after an upgrade

    1.1.0-funcrel is a major release and includes many bug fixes to improve the results produced by the extension. Therefore, after upgrading to 1.1.0 and generating a post upgrade consistency snapshot on unchanged source code, analysis results (objects, links, rules) will be impacted as follows:

    • Less files are skipped during the analysis, providing greater accuracy.
    • More objects are discovered and included in the analysis.
    • Object boundaries are discovered more accurately.
    • Strings and comments are now detected correctly.

    Resolved Issues

    The following table lists all bugs fixed in Fortran 1.1.0-funcrel.

    Internal IDDescriptionImpact?
    FORTRAN-35Snapshot is stuck from 2 daysSnapshot should now complete more quickly.
    FORTRAN-36Functions are named "<unnamed>" when return value type is precedes keyword functionFunction names will be correctly resolved in this situation.
    FORTRAN-40Exception while calculating "Number of Lines of Code (Fortran)"Exception will no longer occur.
    FORTRAN-43Warning "Unable to find the object end for type 'FortranExternalSubroutine'" during analysisThe warning message is no longer displayed. Object end types are now correctly identified.
    FORTRAN-44Warning "Duplicate object of type 'FortranExternalSubroutine' has been detected" is given during analysisThe warning message is no longer displayed.
    FORTRAN-45Warning "Unable to find the object end for type 'FortranInterface'"The warning message is no longer displayed. Object end types are now correctly identified.
    FORTRAN-46Preprocessor log file becomes hugeThe log file will now be much smaller.
    FORTRAN-47Fortran pre-processor processes files of any typeOnly Fortran related files will now be processed.
    FORTRAN-48Fortran pre-processor may fail to create files (intermittent, not easy to replicate)Files without fortran specific extensions are now correctly handled.
    FORTRAN-52Fortran pre-processor process errors out if file cannot be createdA message will now be displayed in the log stating which file cannot be created. Any subsequent files will also be correctly processed instead of being skipped.
    FORTRAN-53Warning "Unable to find the object end for type 'FortranInternalSubroutine'" is given during analysisThe warning message is no longer displayed. Object end types are now correctly identified.
    FORTRAN-54Warning "Duplicate object of type 'FortranInternalSubroutine' has been detected" is given during analysisThe warning message is no longer displayed.
    FORTRAN-55Warning "Unable to find the object end for type 'FortranModule'" is given during analysis The warning message is no longer displayed. Object end types are now correctly identified.
    FORTRAN-56Fortran extension does not consider endfunction and endsubroutine as end of artifactsendfunction and endsubroutine clauses are now correctly identified as the end of artifacts