What Error Checking Will S+ Engineering 2.1 Perform on ADAPT Blocks?
Right now, Composer (up to S+ Engineering 1.5) is the gold standard of configuration support in the INFI 90 family. This noteworthy tool made people forget about DOS CADEWS and WinCAD because it was so much more capable and robust.
One of its deficiencies, however, is that it fails to find many errors that can be a problem. Will S+ Engineering 2.1 (the POSTGRES SQL form) protect users from potentially significant vulnerabilities with useful messages pertaining to ADAPT blocks?
DBDOC detects the following FC24 Adapt block errors and warnings in Composer projects. Will S+ Engineering?
Block adapts a block that is already adapted
- invisible but bad
- nearly always the result of incomplete cloning of valid logic
- always an error in that the intended target block is NOT adapted
- block order can also make the prototype target block get the WRONG value
Spec is illegally adapted
- cold reload can fail to execute
- often indicates AO/L block or other alarm limits that are tunable but not adaptable
Adapt block: Adapted block does not exist
- module can fail to execute
- target block often has been renumbered but the adapt block missed
Adapt block: Spec out of range
- S3 indicates a specification that block S2 does not have
- we do not know what happens when this is loaded and execution attempted
Adapt type mismatch
- can indicate a logic problem
- is often enough legal
Which of these errors does S+ Engineering 2.1 detect? They all can bite.
Whilst not talking specifically about S+ Engineering 2.1 or future versions, the current Composer / S+ Engineering Block Manager and Tuning Line function help to address some of the long standing issues with the configuration of ADAPT, MUX, DEMUX, RECIPE and TSTALM blocks right now, particularly when cloning logic or dropping macros. The Primary Interface Manual for Composer / S+ Engineering has more information.