2009
DOI: 10.1007/978-3-642-02655-3_12
|View full text |Cite
|
Sign up to set email alerts
|

Writing Composable Software with InterpreterLib

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2012
2012
2012
2012

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(2 citation statements)
references
References 12 publications
0
2
0
Order By: Relevance
“…For example, code that does not go through the Game toolchain still has to track roots itself. Second, the evaluator is treated as a single entity, with little support for modularization, especially compared to modular interpreters using monad transformers [11,17]. However, we believe both of these concerns to be…”
Section: Discussion All Three Instantiationsmentioning
confidence: 99%
See 1 more Smart Citation
“…For example, code that does not go through the Game toolchain still has to track roots itself. Second, the evaluator is treated as a single entity, with little support for modularization, especially compared to modular interpreters using monad transformers [11,17]. However, we believe both of these concerns to be…”
Section: Discussion All Three Instantiationsmentioning
confidence: 99%
“…In the context of modularity in interpreters, monads and monad transformers proved to be a very useful abstraction technique [11,17]. The notion of defunctionalized monadic style incorporates the abstraction power of monadic style.…”
Section: Related Workmentioning
confidence: 99%