Differences

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

--- language:langs:refine [2024/08/11 10:26] – [Multiple refinement options] rajit
+++ language:langs:refine [2024/08/11 10:31] (current) – [Multiple refinement options] rajit
@@ Line 98: / Line 98: @@
 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//.