|
@@ -34,7 +34,7 @@ The SCCD discussed in this thesis is a fork from the original SCCD. The most imp
|
|
|
|
|
|
\begin{description}
|
|
|
\item[More semantic options]
|
|
|
- The main goal of this thesis. On top of the semantic options supported in original SCCD, the following options were added: Big-Step Maximality: \textsc{Syntactic}, Combo-Step Maximality: \textsc{Combo Take One}, \textsc{Combo Take Many}, Memory Protocol: \textsc{Big Step}, \textsc{Combo Step}, \textsc{Small Step}, Priority: \textsc{Arena-Parent}, \textsc{Arena-Child}.
|
|
|
+ The main goal of this thesis. On top of the semantic options supported in original SCCD, the following options were added: Big-Step Maximality: \textsc{Syntactic}, Combo-Step Maximality: \textsc{Combo Take One}, \textsc{Combo Take Many}, \textsc{Combo Syntactic}, Memory Protocol: \textsc{Big Step}, \textsc{Combo Step}, \textsc{Small Step}, Priority: \textsc{Arena-Parent}, \textsc{Arena-Child}.
|
|
|
|
|
|
\item[Action language]
|
|
|
In the original SCCD, action code had to be written in the same language as the target language of compilation, making models non-portable. This was only a temporary solution, the plan was to add an action language eventually. Another reason for integrating an action language is to have precise control over Memory Protocol semantics. Therefore, SCCD now has a built-in (textual) statically type-checked action language.
|