Proceedings of the 2015 Workshop on Partial Evaluation and Program Manipulation 2015
DOI: 10.1145/2678015.2682541
|View full text |Cite
|
Sign up to set email alerts
|

Incremental Evaluation of Higher Order Attributes

Abstract: Compilers, amongst other programs, often work with data that (slowly) changes over time. When the changes between subsequent runs of the compiler are small, one would hope the compiler to incrementally update its results, resulting in much lower running times. However, the manual construction of an incremental compiler is very hard and error prone and therefore usually not an option.Attribute grammars provide an attractive way of constructing compilers, as they are compositional in nature and allow for aspect … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
2
0

Year Published

2018
2018
2018
2018

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(2 citation statements)
references
References 21 publications
(15 reference statements)
0
2
0
Order By: Relevance
“…Moreover, when research branches out, the running examples do not work in other branches. For example, classical attribute grammars [14,23,24] are extended in aggregate AGs [9], remote AGs [1], reference AGs (RAGs) [17], and various higherorder AGs [18,20,15,2,3], but these extensions do not support each others running examples while most authors claim it is a general framework for building compilers. (One such example is that aggregate AGs (1986) [9] optimize edits on map data Figure 1 Trade-off between specificity and generality in name binding DSLs.…”
Section: Every Dsl Paper Has Its Own Running Examplementioning
confidence: 99%
See 1 more Smart Citation
“…Moreover, when research branches out, the running examples do not work in other branches. For example, classical attribute grammars [14,23,24] are extended in aggregate AGs [9], remote AGs [1], reference AGs (RAGs) [17], and various higherorder AGs [18,20,15,2,3], but these extensions do not support each others running examples while most authors claim it is a general framework for building compilers. (One such example is that aggregate AGs (1986) [9] optimize edits on map data Figure 1 Trade-off between specificity and generality in name binding DSLs.…”
Section: Every Dsl Paper Has Its Own Running Examplementioning
confidence: 99%
“…Presented at the LangDevCon in 2018 (http://langdevcon.org/) 2. Presented at the Dutch Software Engineering Symposium in 2016 (http://www.sensymposium.nl/history/2016/program/).18:5We should Stop Claiming Generality in our DSL Papers…”
mentioning
confidence: 99%