Reusing non-functional concerns across languages

Song, Myoungkyu; Tilevich, Eli

doi:10.1145/2162049.2162076

Cited by 3 publications

(3 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Also, Trudel et al [17] discuss source-to-source translation of C to Eiffel, Verdoolaege et al [18] discuss a source-to-source compiler of a sequential program for parallel execution on a modern GPU, and Song and Tilevich [19] discuss preserving non-functional aspects of languages in source-to-source translations, Source-to-source translation has also been used for program optimization or development in a given language. As another example of this approach, Standish et al [23] discuss using interactive source-to-source transformations in the context of program improvement and program refinement.…”

Section: Past Workmentioning

confidence: 99%

Source-to-Source Translation and Software Engineering

Plaisted¹

2013

JSEA

View full text Add to dashboard Cite

Source-to-source translation of programs from one high level language to another has been shown to be an effective aid to programming in many cases. By the use of this approach, it is sometimes possible to produce software more cheaply and reliably. However, the full potential of this technique has not yet been realized. It is proposed to make source-to-source translation more effective by the use of abstract languages, which are imperative languages with a simple syntax and semantics that facilitate their translation into many different languages. By the use of such abstract languages and by translating only often-used fragments of programs rather than whole programs, the need to avoid writing the same program or algorithm over and over again in different languages can be reduced. It is further proposed that programmers be encouraged to write often-used algorithms and program fragments in such abstract languages. Libraries of such abstract programs and program fragments can then be constructed, and programmers can be encouraged to make use of such libraries by translating their abstract programs into application languages and adding code to join things together when coding in various application languages. This approach can also improve program reliability, because it is only necessary to verify the abstract programs once instead of verifying them separately in each application language. Also, this approach makes it possible to generate code faster than programming from scratch each time. This approach is compared to the use of libraries and to other methods in current use for communication between programming languages and translation between languages.

show abstract

Section: Past Workmentioning

confidence: 99%

Source-to-Source Translation and Software Engineering

Plaisted¹

2013

JSEA

View full text Add to dashboard Cite

show abstract

“…Song and Tilevich [24] reuse the concern implementations in established languages from emerging languages by translating metadata alongside that of the main source code. By contrast, TAE-JS expresses concern implementations within the same language declaratively.…”

Section: Supporting Separation Of Concerns Via Metadatamentioning

confidence: 99%

Tae-Js

Song

Tilevich

2013

Proceedings of the 2013 International Conference on Principles and Practices of Programming on the Java Platform: Virtual Machi

Self Cite

View full text Add to dashboard Cite

Recent state-of-the-art approaches enhance JavaScript programs with concerns (e.g., persistence, security, transactions, etc.) by modifying the source code by hand to use special libraries. As a result, adding concerns to a JavaScript program creates divergent codebases that must be maintained separately. At the core of the problem is that JavaScript lacks metadata to express concerns declaratively. In this paper, we present a declarative approach to enhancing JavaScript programs that applies the Java annotations infrastructure to JavaScript, without extending the JavaScript language. An IDE combines JavaScript and Java during the development, but processes the languages separately. Programmers declare how concerns should be added to a JavaScript program using Java annotations. Based on the annotations, a code generator synthesizes aspect code that adds the specified concerns. Although these enhancements are implemented as third-party libraries, our approach can transparently insert them into JavaScript programs given a declarative specification.

show abstract

“…To effectively express metadata invariants, we introduce a domain-specific language that we call the Metadata Invariants Language (MIL), which takes advantage of the powerful program query constructs we have developed in our prior work on improving metadata reusability [21], [23].…”

Section: Introductionmentioning

confidence: 99%

Metadata invariants: Checking and inferring metadata coding conventions

Song

Tilevich

2012

2012 34th International Conference on Software Engineering (ICSE)

Self Cite

View full text Add to dashboard Cite

Abstract-As the prevailing programming model of enterprise applications is becoming more declarative, programmers are spending an increasing amount of their time and efforts writing and maintaining metadata, such as XML or annotations. Although metadata is a cornerstone of modern software, automatic bug finding tools cannot ensure that metadata maintains its correctness during refactoring and enhancement. To address this shortcoming, this paper presents metadata invariants, a new abstraction that codifies various naming and typing relationships between metadata and the main source code of a program. We reify this abstraction as a domain-specific language. We also introduce algorithms to infer likely metadata invariants and to apply them to check metadata correctness in the presence of program evolution. We demonstrate how metadata invariant checking can help ensure that metadata remains consistent and correct during program evolution; it finds metadata-related inconsistencies and recommends how they should be corrected. Similar to static bug finding tools, a metadata invariant checker identifies metadata-related bugs as a program is being refactored and enhanced. Because metadata is omnipresent in modern software applications, our approach can help ensure the overall consistency and correctness of software as it evolves.

show abstract

Reusing non-functional concerns across languages

Cited by 3 publications

References 11 publications

Source-to-Source Translation and Software Engineering

Source-to-Source Translation and Software Engineering

Tae-Js

Metadata invariants: Checking and inferring metadata coding conventions

Contact Info

Product

Resources

About