glen/spoofax_prop
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

fix: Get repository working again

Browse source 
The main actions taking to restore spoofax_prop to correct operation
   are not really reflected in this commit; they consisted of
   switching to a Spoofax distribution of Eclipse and
updating/rebuilding
   the project in various ways. However, all of the steps are now
   documented here, and the narrative is extended to include the
   first examples.

   Resolves #1.
This commit is contained in:
Glen Whitney 2021-01-14 10:19:35 -08:00
parent ba6084513f
commit 8536d6a469
5 changed files with 67 additions and 64 deletions
Download patch file Download diff file Expand all files Collapse all files

18
trans/prop-eval-rules.str
View file

@ -4,7 +4,7 @@ Title: Running a Strategy
## Running a Strategy
The first example of running a Stratego strategy
in the {! ../docrefs/manual.md !} } is that of _evaluating_ an AST,
in the {! ../docrefs/manual.md !} is that of _evaluating_ an AST,
via the `prop-eval-rules` module in {! ../docrefs/sec4.1.md !}. This page
describes the most straightforward way to run this same strategy
in the Spoofax Eclipse IDE.
@ -87,7 +87,7 @@ It's just the one line `Manual` in the `imports` section that we have added. The
{! ../editor/Manual.esv !}
```
Note that the quoted string on the `action` line is the text label of the menu
item in the "Manual" submenu, and the identifier on its right-hand side is the
item in the "Manual" submenu, and the first identifier on its right-hand side is the
Stratego action to call. But note that `do-eval` is not the same identifier as
`eval` in our last Stratego file above. That's because the Stratego invocation
caused by an ESV action item has a specific, multi-item argument list, whereas
@ -129,7 +129,15 @@ file `syntax/examples/sec4.1_test1.spl`:
{! ../syntax/examples/sec4.1_test1.spl !}
```
and select "Spoofax > Manual > prop-eval" from the menu bar to produce:
[CONTINUE HERE ONCE THIS WORKS]
```
{! ../syntax/examples/sec4.1_test1.eval.aterm !}
```
You can do the same with test2:
```SPL
{! ../syntax/examples/sec4.1_test2.spl !}
```
to produce
```
{! ../syntax/examples/sec4.1_test2.eval.aterm !}
```
**/