Normalizing object-oriented class styles in JavaScript

Gama, Widd; Alalfi, Manar H.; Cordy, James R.; Dean, Thomas R.

doi:10.1109/wse.2012.6320536

Cited by 9 publications

(10 citation statements)

References 10 publications

(9 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The implementation in Listing 1.1 represents one possibility of class emulation in JavaScript. Some variations are possible, like implementing methods inside/outside class constructors and using anonymous/non-anonymous functions [8,11].…”

Section: Class Emulation In Legacy Javascript Codementioning

confidence: 99%

Refactoring Legacy JavaScript Code to Use Classes: The Good, The Bad and The Ugly

Silva¹,

Valente

Bergel

2017

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. JavaScript systems are becoming increasingly complex and large. To tackle the challenges involved in implementing these systems, the language is evolving to include several constructions for programmingin-the-large. For example, although the language is prototype-based, the latest JavaScript standard, named ECMAScript 6 (ES6), provides native support for implementing classes. Even though most modern web browsers support ES6, only a very few applications use the class syntax. In this paper, we analyze the process of migrating structures that emulate classes in legacy JavaScript code to adopt the new syntax for classes introduced by ES6. We apply a set of migration rules on eight legacy JavaScript systems. In our study, we document: (a) cases that are straightforward to migrate (the good parts); (b) cases that require manual and ad-hoc migration (the bad parts); and (c) cases that cannot be migrated due to limitations and restrictions of ES6 (the ugly parts). Six out of eight systems (75%) contain instances of bad and/or ugly cases. We also collect the perceptions of JavaScript developers about migrating their code to use the new syntax for classes.

show abstract

Section: Class Emulation In Legacy Javascript Codementioning

confidence: 99%

Refactoring Legacy JavaScript Code to Use Classes: The Good, The Bad and The Ugly

Silva¹,

Valente

Bergel

2017

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…Gama et al identify 5 styles for implementing methods in JavaScript: inside/outside constructor functions using anonymous/nonanonymous functions and using prototypes. Their main goal is to implement an automated approach to normalizing JavaScript code to a single consistent object‐oriented style.…”

Section: Related Workmentioning

confidence: 99%

Identifying Classes in Legacy JavaScript Code

et al. 2017

View full text Add to dashboard Cite

International audienceJavaScript is the most popular programming language for the Web. Although the language is prototype-based, developers can emulate class-based abstractions in JavaScript to master the increasing complexity of their applications. Identifying classes in legacy JavaScript code can support these developers at least in the following activities: (i) program comprehension; (ii) migration to the new JavaScript syntax that supports classes; and (iii) implementation of supporting tools, including IDEs with class-based views and reverse engineering tools. In this paper, we propose a strategy to detect class-based abstractions in the source code of legacy JavaScript systems. We report on a large and in-depth study to understand how class emulation is employed, using a dataset of 918 JavaScript applications available on GitHub. We found that almost 70% of the JavaScript systems we study make some usage of classes. We also performed a field study with the main developers of 60 popular JavaScript systems in order to validate our findings. The overall results range from 97% to 100% for precision, from 70% to 89% for recall, and from 82% to 94% for F-score

show abstract

“…The software follows an objectoriented approach. JavaScript does not support class-based inheritance as in C++ (or similar languages), rather, it implements behavior reuse through prototype-based inheritance [13]. If a desired property is not found on an object, the property access is delegated up the prototype chain.…”

Section: Javascript and Web Applicationsmentioning

confidence: 99%

The Majorana Parts Tracking Database

Abgrall

Aguayo

Avignone

et al. 2015

Nuclear Instruments and Methods in Physics Research Section A:

View full text Add to dashboard Cite

The Majorana Demonstrator is an ultra-low background physics experiment searching for the neutrinoless double beta decay of 76 Ge. The Majorana Parts Tracking Database is used to record the history of components used in the construction of the Demonstrator. The tracking implementation takes a novel approach based on the schema-free database technology CouchDB. Transportation, storage, and processes undergone by parts such as machining or cleaning are linked to part records. Tracking parts provides a great logistics benefit and an important quality assurance reference during construction. In addition, the location history of parts provides an estimate of their exposure to cosmic radiation. A web application for data entry and a radiation exposure calculator have been developed as tools for achieving the extreme radio-purity required for this rare decay search.

show abstract

Normalizing object-oriented class styles in JavaScript

Cited by 9 publications

References 10 publications

Refactoring Legacy JavaScript Code to Use Classes: The Good, The Bad and The Ugly

Refactoring Legacy JavaScript Code to Use Classes: The Good, The Bad and The Ugly

Identifying Classes in Legacy JavaScript Code

The Majorana Parts Tracking Database

Contact Info

Product

Resources

About