lyx/obsidian-yanxin
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Archive 12 API mapping research papers (related work for PhD)

Browse Source 
Reference papers on API mapping, migration, and evolution collected during
PhD research (2018). Topics include: API usage adaptation (LibSync),
statistical API mapping mining (StaMiner, MAM), API mapping via vector
representations (Word2Vec), text mining for API mappings (TMAP),
library migration graphs, framework evolution (AURA), class library
migration refactoring, and API specification inference (Doc2Spec).
This commit is contained in:
Yanxin Lu
2026-04-06 12:06:56 -07:00
parent b85169f4e7
commit ff146a9362
24 changed files with 6949 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
documents/academic/paper/api_mappings/balaban_05_migration.md Normal file
View File

@@ -0,0 +1,17 @@
---
category: academic
type: academic
person: Yanxin Lu
date: 2005
source: balaban_05_migration.pdf
---
# Refactoring Support for Class Library Migration
Ittai Balaban (NYU), Frank Tip, Robert Fuhrer (IBM T.J. Watson Research Center)
OOPSLA 2005
As object-oriented class libraries evolve, classes are occasionally deprecated in favor of others with roughly the same functionality. In Java, for example, Hashtable has been superseded by HashMap, and Iterator is now preferred over Enumeration. Migrating client applications to use the new idioms is desirable, but making the required changes to declarations and allocation sites can be quite labor-intensive. Moreover, migration becomes complicated if a legacy class is not completely equivalent to its replacement, or if multiple interdependent classes must be migrated simultaneously.
The authors present an approach in which mappings between legacy classes and their replacements are specified by the programmer. Then, an analysis based on type constraints determines where declarations and allocation sites can be updated. The method was implemented in Eclipse, and evaluated on a number of Java applications. On average, the tool could migrate more than 90% of the references to legacy classes.