Custom Query (74 matches)

Change the semantics of extendsInNoOverSpecificRunsOn in #75 to only consider "pure" aliases where there shall be no definitions within the extending component and only one level shall be considered. The corresponding configuration setting shall be switched to aliasInNoOverSpecificRunsOn. The documentation and examples shall be updated to reflect the changes.

Add optional support for considering inherited component members within no over specific runs on:

    //base component
    type component componentWithDefinition {
        timer definedTimer;
    }


    //alias	/ extension
    type component directAlias extends componentWithDefinition {
        
    }

    //multi alias /extension
    type component multiAlias extends directAlias {
        
    }

    //good - via direct alias
    function someFunctionOnMultiAlias ()
    runs on directAlias {
        definedTimer.start ( 10.0 );
    }


    //good - via multi alias
    function someFunctionOnMultiAlias ()
    runs on multiAlias {
        definedTimer.start ( 10.0 );
    }

The statistics shown at the end of the report are not reflecting the real number of warnings on this feature.

Playing around with and without the settings and excluding some types and the number of warnings shown are, as planned, different. When checkNoUninitialisedVariables is disabled the statistics are ok. When it is enabled I think it marks always as if no specific type was excluded.