2017 IEEE 24th International Conference on Software Analysis, Evolution and Reengineering (SANER) 2017
DOI: 10.1109/saner.2017.7884679
|View full text |Cite
|
Sign up to set email alerts
|

Modernizing domain-specific languages with XMLText and IntellEdit

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2018
2018
2024
2024

Publication Types

Select...
2
1

Relationship

1
2

Authors

Journals

citations
Cited by 3 publications
(2 citation statements)
references
References 8 publications
0
2
0
Order By: Relevance
“…GrammarOptimizer is designed to modify grammars that Xtext generated out of meta-models. An alternative to this post-processing approach is to directly modify the Xtext grammar generator as, e.g., in XMLText (Neubauer et al, 2015(Neubauer et al, , 2017. However, we deliberately chose a post-processing approach, because the application of conventional regular expressions enables the transferability to other recent language development frameworks like Langium (TypeFox GmbH, 2022) or textX (Dejanović Furthermore, as the implementation of an Xtext grammar generator necessarily depends on many version-specific internal aspects of Xtext, the post-processing approach using regular expressions is considerably more maintainable.…”
Section: Post-processing Vs Changing Grammar Generationmentioning
confidence: 99%
“…GrammarOptimizer is designed to modify grammars that Xtext generated out of meta-models. An alternative to this post-processing approach is to directly modify the Xtext grammar generator as, e.g., in XMLText (Neubauer et al, 2015(Neubauer et al, , 2017. However, we deliberately chose a post-processing approach, because the application of conventional regular expressions enables the transferability to other recent language development frameworks like Langium (TypeFox GmbH, 2022) or textX (Dejanović Furthermore, as the implementation of an Xtext grammar generator necessarily depends on many version-specific internal aspects of Xtext, the post-processing approach using regular expressions is considerably more maintainable.…”
Section: Post-processing Vs Changing Grammar Generationmentioning
confidence: 99%
“…For example, if one had a transformation from XSD to Ecore, and an assistant for Ecore (translating Ecore to Extremo's common data model), then an assistant for XSD can be built by first translating into Ecore and then invoking the Ecore assistant. This is the way we implemented the XsdAssistant (see Figure 4) [42,43,44].…”
Section: The Core Subsystemmentioning
confidence: 99%