73dfcd6c1e
ci/woodpecker/push/build Pipeline was successful
Details
- The current implementation triggers a warning when rejected classes are find in the monitor, and an error if monitor_strict_checking is enable. It follows these rules: Inside the scope of a monitor, all instances of classes mentioned in its accepts_clause (the ∗‹accept-set›) have to appear in the order specified by the regular expression. Instances not covered by an accept-set may freely occur. Monitors may additionally contain a rejects_clause with a list of class-ids (the reject-list). This allows specifying ranges of admissible instances along the class hierarchy: - a superclass in the reject-list and a subclass in the accept-expression forbids instances superior to the subclass, and - a subclass S in the reject-list and a superclass T in the accept-list allows instances of superclasses of T to occur freely, instances of T to occur in the specified order and forbids instances of S. - No message is triggered for the free classes, but two theory options, free_class_in_monitor_checking and free_class_in_monitor_strict_checking, are added and can be used if we want to trigger warnings or errors, in the case we do not want free classes inside a monitor. - Fix the checking warning when defining a monitor, as the monitor was added to the monitor table and then the instance of the monitor was added to the theory. So a monitor had the bad behavior to check itself. |
||
---|---|---|
.. | ||
DOF | ||
document-templates | ||
ontologies | ||
scala | ||
tests | ||
ROOT | ||
ROOTS |