Differences

This shows you the differences between two versions of the page.

--- language:langs:refine [2024/08/11 10:25] – [Nested refinements] rajit
+++ language:langs:refine [2025/04/21 19:58] (current) – [Refinement overrides] rajit
@@ Line 95: / Line 95: @@
 ===== Multiple refinement options =====
+While the nested refinement approach works nicely when designs are recursively refined, it may not
+be suitable for transformations where an existing refinement block needs to be completely replaced.
+ACT has a mechanism to support this in the following manner:
+<code act>
+refine {
+    inst i1;
+    chp { ... }
+}
+refine<2> {
+    inst j1;
+    prs { ... }
+}
+</code>
+In this case, "-ref=2" will //replace// the first refine block with the second. In other words, instance ''i1'' will not
+be created, and ''-ref=2'' will select instance ''j2'' and the ''prs { ... }'' body.
+In general, a refine block has an associated integer refinement level (the default is one). When ACT processes a block with refinement level //r//, it searches for the largest refinement block with level that is at most //r//. (Note: this may be no block, in which case the block is processed as normal.) If a refine block with level //l// is found, then it processes all non-language constructs within the block and then expands the refinement block with level //l// by decrementing the current refinement level by //l//.
+===== Refinement overrides =====
+Sometimes a refinement body needs to [[language:impl#overrides|override]] types. To support this, refinement bodies can be accompanied by refinement overrides. These are overrides that are only applied when the refinement is used.
+The syntax for providing refinement overrides is below:
+<code act>
+refine<2>  +{ e1of2 l; } {
+       inst1 i1;
+       ...
+ }
+</code>
+This will apply the refinement override for ''l'' when this particular refinement body is selected.
+</code>