Precompile

Available from TwinCAT 3.1 Build 4026

Most Static Analysis rules can already be checked during precompilation. For the detection of such rule violations no explicit execution of the Static Analysis is necessary, but the check already takes place on the basis of the precompile information during editing. The checking of a rule during precompilation takes place only if the rule is enabled in the Static Analysis settings. Please note the options for configuring the precompile behavior, see: Rules.

If a rule violation is detected during pre-compilation, it is immediately indicated by a wavy underline in the declaration editor or the ST editor. The precompile messages also appear in the error list (see also: Error list).

Available rules

Not available:

Please note that the following rules cannot be checked during precompilation.

• SA0004: Multiple write access on output
• SA0006: Write access from several tasks
• SA0016: Gaps in structures
• SA0027: Multiple usage of name
• SA0028: Overlapping memory areas
• SA0042: Usage of different access paths
• SA0100: Variables greater than <n> bytes
• SA0103: Concurrent access on not atomic data
• SA0105: Multiple instance calls
• SA0150: Violations of lower or upper limits of the metrics
• SA0160: Recursive calls
• SA0175: Suspicious operation on string

Available:

All other rules are checked on the basis of the precompile information.