Synopsis Include the results of an interactive session of the Rascal interpreter.
Syntax
<screen OptErrors>RascalCode</screen>
Description The commands in the
The following is supported:
RascalCode are executed and
they are show together with the response of the Rascal system.
The following is supported:
- Lines that start with
//are formatted as ordinary text. This makes it possible to write a story with interspersed Rascal code. - Comments in the code of the form
/*Number*/are replaced by numbered markers such as
If any error messages are generated or exceptions are raised, they will be logged as warnings. The precise set of words that triggers a warning is: -
Exception,exception -
Error,error -
cancelled. -
Timeout,timeout.
OptErrors is non-empty, it is assumed that the error is expected and it will not be logged.
Examples The text:
will be shown as:
<screen>1 + 2;</screen>
will be shown as:
rascal>1 + 2;
int: 3
Benefits
- All code in a concept is actually executed before it is included in an HTML file.
- In the warnings, an overview is maintained of code fragments that produce unexpected errors.
Pitfalls
-
<screen>and</screen>should start at the begin of a line. - The
RascalCodein a screen is executed in a fresh Rascal Interpreter. Hence no state can be carried over between screens.