2002
DOI: 10.1016/s0950-5849(02)00104-0
|View full text |Cite
|
Sign up to set email alerts
|

Source transformation in software engineering using the TXL transformation system

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
65
0

Year Published

2004
2004
2022
2022

Publication Types

Select...
4
4
2

Relationship

0
10

Authors

Journals

citations
Cited by 90 publications
(65 citation statements)
references
References 14 publications
(14 reference statements)
0
65
0
Order By: Relevance
“…We have applied the protection mechanism on five open source network server programs, as shown in Table 1. Source code transformation is done by using TXL [26], a special-purpose programming language designed for software analysis and source code transformation. We extend the Gemini tool [24], which transforms source code to reposition stack-based buffers on the heap by using TXL, to protect local buffers with guard pages.…”
Section: Performance Evaluationmentioning
confidence: 99%
“…We have applied the protection mechanism on five open source network server programs, as shown in Table 1. Source code transformation is done by using TXL [26], a special-purpose programming language designed for software analysis and source code transformation. We extend the Gemini tool [24], which transforms source code to reposition stack-based buffers on the heap by using TXL, to protect local buffers with guard pages.…”
Section: Performance Evaluationmentioning
confidence: 99%
“…In essence this step converts the concrete syntax into an abstract syntax better suited to a particular analysis. Most parsers are compiler-based and process the entire language [27,35]. When only a subset of the concrete syntax must be processed, lighter-weight techniques can be applied.…”
Section: Anatomy Of a Source Code Analysismentioning
confidence: 99%
“…Stage one uniquely names all entities in the project while extracting the entity and relationship facts. This process is accomplished with a TXL program using syntactic pattern matching [2,4]. At this point, the method call facts are not uniquely identified since we do not have sufficient information to identify which package or class the method being called belongs to.…”
Section: Project Watchermentioning
confidence: 99%