Scoping an external dynamic rules generates an error with the Stratego editor. The external definition is read from a rtree.

Rtree contains:

Specification(
  [ ...
    , Strategies(
    [ ...
    , ExtSDef("Rename", [], [])
    ]
  ]
)

Source file contains:

{| Rename:
    Rename;
    ...
|}

The call to Rename works fine, but the rule scope generates an error marker.

Submitted by Nathan Bruning on 17 May 2010 at 18:10

The standard Stratego compiler doesn’t check for validity of rule scopes: it can say {| Anything: ... |}. The rtrees also don’t provide any information about the dynamic rules (other than the fact that there’s an external strategy with that name). Maybe we should just allow scopes for names of external strategies? Like {| map: ... |} :)