<?xml version="1.0" encoding="UTF-8"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-07-23T18:19:13Z</responseDate>
  <request identifier="6119" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:6119</identifier>
        <datestamp>2024-03-06T10:38:02Z</datestamp>
        <setSpec>ddc:004</setSpec>
        <setSpec>open_access</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>Transforming Programs between APIs with Many-to-Many Mappings</dc:title>
          <dc:creator>Wang, Chenglong</dc:creator>
          <dc:creator>Jiang, Jiajun</dc:creator>
          <dc:creator>Li, Jun</dc:creator>
          <dc:creator>Xiong, Yingfei</dc:creator>
          <dc:creator>Luo, Xiangyu</dc:creator>
          <dc:creator>Zhang, Lu</dc:creator>
          <dc:creator>Hu, Zhenjiang</dc:creator>
          <dc:subject>Program transformation</dc:subject>
          <dc:subject>API migration</dc:subject>
          <dc:description>Transforming programs between two APIs or different versions of&#13;
the same API is a common software engineering task. However,&#13;
existing languages supporting for such transformation cannot&#13;
satisfactorily handle the cases when the relations between&#13;
elements in the old API and the new API are many-to-many&#13;
mappings: multiple invocations to the old API are supposed to be&#13;
replaced by multiple invocations to the new API. Since the&#13;
multiple invocations of the original APIs may not appear&#13;
consecutively and the variables in these calls may have different&#13;
names, writing a tool correctly to cover all such invocation&#13;
cases is not an easy task.  In this paper we propose a novel&#13;
guided-normalization approach to address this problem. Our core&#13;
insight is that programs in different forms can be&#13;
semantics-equivalently normalized into a basic form guided by&#13;
transformation goals, and developers only need to write rules for&#13;
the basic form to address the transformation. Based on this&#13;
approach, we design a declarative program transformation&#13;
language, PATL, for adapting Java programs between different&#13;
APIs. PATL has simple syntax and basic semantics to handle&#13;
transformations only considering consecutive statements inside&#13;
basic blocks, while with guided-normalization, it can be extended&#13;
to handle complex forms of invocations. Furthermore, PATL ensures&#13;
that the user-written rules would not accidentally break def-use&#13;
relations in the program.  We formalize the semantics of PATL on&#13;
Middleweight Java and prove the semantics-preserving property of&#13;
guided-normalization. We also evaluated our language with three&#13;
non-trivial case studies: i.e. updating Google Calendar API,&#13;
switching from JDom to Dom4j, and switching from Swing to&#13;
SWT. The result is encouraging; it shows that our language allows&#13;
successful transformations of real world programs with a small&#13;
number of rules and little manual resolution.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Chenglong Wang and Jiajun Jiang and Jun Li and Yingfei Xiong and Xiangyu Luo and Lu Zhang and Zhenjiang Hu</dc:contributor>
          <dc:date>2016</dc:date>
          <dc:relation>Is Part Of LIPIcs, Volume 56, 30th European Conference on Object-Oriented Programming (ECOOP 2016)</dc:relation>
          <dc:type>InProceedings</dc:type>
          <dc:type>Text</dc:type>
          <dc:type>doc-type:ResearchArticle</dc:type>
          <dc:type>publishedVersion</dc:type>
          <dc:format>application/pdf</dc:format>
          <dc:identifier>doi:10.4230/LIPIcs.ECOOP.2016.25</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-61195</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/LIPIcs.ECOOP.2016.25</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by/3.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
