Clones and Macro Co-changes

Clones and Macro Co-changes. Lozano, A., Jaafar, F., Mens, K., & Gu�h�neuc, Y. In G�de, N. & Higo, Y., editors, Proceedings of the 8th International Workshop on Software Clones (IWSC), February, 2014. Electronic Communications of the EASST. 15 pages.

Paper abstract bibtex

Ideally, any change that modifies the similar parts of a cloned code snippet should be propagated to all its duplicates. In practice however, consistent propagation of changes in clones does not always happen. Current evidence indicates that clone families have a 50\NOchance of having consistent changes. This paper measures cloning and co-changes at file level as a proxy to assess the frequency of consistent changes. Given that changes to a clone group are not necessarily propagated in the same commit transaction (i.e., late propagations), our analysis uses macro co-changes instead of the traditional definition of co-changes. Macro changes group bursts of changes that are closer among themselves than to other changes, regardless of author or message. Then, macro co-changes are sets of files that change in the same macro changes. Each cloned file is tagged depending on whether any of the files with which it macro co-changes is cloned with it (during the macro change) or not. Contrary to previous results, we discovered that most of the cloned files macro co-change \emphonly with files with which they share clones. Thus providing evidence that macro changes are appropriate to study the conjecture of clones requiring co-changes, and indicating that consistent changes might be the norm in cloned code.

@INPROCEEDINGS{Lozano14-IWSC-ClonesMacroCochanges,
   AUTHOR       = {Angela Lozano and Fehmi Jaafar and Kim Mens and 
      Yann-Ga�l Gu�h�neuc},
   BOOKTITLE    = {Proceedings of the 8<sup>th</sup> International Workshop on Software Clones (IWSC)},
   TITLE        = {Clones and Macro Co-changes},
   YEAR         = {2014},
   OPTADDRESS   = {},
   OPTCROSSREF  = {},
   EDITOR       = {Nils G�de and Yoshiki Higo},
   MONTH        = {February},
   NOTE         = {15 pages.},
   OPTNUMBER    = {},
   OPTORGANIZATION = {},
   OPTPAGES     = {},
   PUBLISHER    = {Electronic Communications of the EASST},
   OPTSERIES    = {},
   OPTVOLUME    = {},
   KEYWORDS     = {Topic: <b>Evolution patterns</b>, Venue: <i>IWSC</i>},
   URL          = {http://www.ptidej.net/publications/documents/IWSC14.doc.pdf},
   PDF          = {http://www.ptidej.net/publications/documents/IWSC14.ppt.pdf},
   ABSTRACT     = {Ideally, any change that modifies the similar parts of a 
      cloned code snippet should be propagated to all its duplicates. In 
      practice however, consistent propagation of changes in clones does 
      not always happen. Current evidence indicates that clone families 
      have a 50\NOchance of having consistent changes. This paper measures 
      cloning and co-changes at file level as a proxy to assess the 
      frequency of consistent changes. Given that changes to a clone group 
      are not necessarily propagated in the same commit transaction (i.e., 
      late propagations), our analysis uses macro co-changes instead of the 
      traditional definition of co-changes. Macro changes group bursts of 
      changes that are closer among themselves than to other changes, 
      regardless of author or message. Then, macro co-changes are sets of 
      files that change in the same macro changes. Each cloned file is 
      tagged depending on whether any of the files with which it macro 
      co-changes is cloned with it (during the macro change) or not. 
      Contrary to previous results, we discovered that most of the cloned 
      files macro co-change \emph{only} with files with which they share 
      clones. Thus providing evidence that macro changes are appropriate to 
      study the conjecture of clones requiring co-changes, and indicating 
      that consistent changes might be the norm in cloned code.}
}

Downloads: 0

{"_id":"MLMxyzRjKkeWE2pE7","bibbaseid":"lozano-jaafar-mens-guhneuc-clonesandmacrocochanges-2014","downloads":0,"creationDate":"2018-01-17T20:29:42.281Z","title":"Clones and Macro Co-changes","author_short":["Lozano, A.","Jaafar, F.","Mens, K.","Gu�h�neuc, Y."],"year":2014,"bibtype":"inproceedings","biburl":"http://www.yann-gael.gueheneuc.net/Work/Publications/Biblio/complete-bibliography.bib","bibdata":{"bibtype":"inproceedings","type":"inproceedings","author":[{"firstnames":["Angela"],"propositions":[],"lastnames":["Lozano"],"suffixes":[]},{"firstnames":["Fehmi"],"propositions":[],"lastnames":["Jaafar"],"suffixes":[]},{"firstnames":["Kim"],"propositions":[],"lastnames":["Mens"],"suffixes":[]},{"firstnames":["Yann-Ga�l"],"propositions":[],"lastnames":["Gu�h�neuc"],"suffixes":[]}],"booktitle":"Proceedings of the 8th International Workshop on Software Clones (IWSC)","title":"Clones and Macro Co-changes","year":"2014","optaddress":"","optcrossref":"","editor":[{"firstnames":["Nils"],"propositions":[],"lastnames":["G�de"],"suffixes":[]},{"firstnames":["Yoshiki"],"propositions":[],"lastnames":["Higo"],"suffixes":[]}],"month":"February","note":"15 pages.","optnumber":"","optorganization":"","optpages":"","publisher":"Electronic Communications of the EASST","optseries":"","optvolume":"","keywords":"Topic: Evolution patterns, Venue: IWSC","url":"http://www.ptidej.net/publications/documents/IWSC14.doc.pdf","pdf":"http://www.ptidej.net/publications/documents/IWSC14.ppt.pdf","abstract":"Ideally, any change that modifies the similar parts of a cloned code snippet should be propagated to all its duplicates. In practice however, consistent propagation of changes in clones does not always happen. Current evidence indicates that clone families have a 50\\NOchance of having consistent changes. This paper measures cloning and co-changes at file level as a proxy to assess the frequency of consistent changes. Given that changes to a clone group are not necessarily propagated in the same commit transaction (i.e., late propagations), our analysis uses macro co-changes instead of the traditional definition of co-changes. Macro changes group bursts of changes that are closer among themselves than to other changes, regardless of author or message. Then, macro co-changes are sets of files that change in the same macro changes. Each cloned file is tagged depending on whether any of the files with which it macro co-changes is cloned with it (during the macro change) or not. Contrary to previous results, we discovered that most of the cloned files macro co-change \\emphonly with files with which they share clones. Thus providing evidence that macro changes are appropriate to study the conjecture of clones requiring co-changes, and indicating that consistent changes might be the norm in cloned code.","bibtex":"@INPROCEEDINGS{Lozano14-IWSC-ClonesMacroCochanges,\r\n AUTHOR = {Angela Lozano and Fehmi Jaafar and Kim Mens and \r\n Yann-Ga�l Gu�h�neuc},\r\n BOOKTITLE = {Proceedings of the 8th International Workshop on Software Clones (IWSC)},\r\n TITLE = {Clones and Macro Co-changes},\r\n YEAR = {2014},\r\n OPTADDRESS = {},\r\n OPTCROSSREF = {},\r\n EDITOR = {Nils G�de and Yoshiki Higo},\r\n MONTH = {February},\r\n NOTE = {15 pages.},\r\n OPTNUMBER = {},\r\n OPTORGANIZATION = {},\r\n OPTPAGES = {},\r\n PUBLISHER = {Electronic Communications of the EASST},\r\n OPTSERIES = {},\r\n OPTVOLUME = {},\r\n KEYWORDS = {Topic: Evolution patterns, Venue: IWSC},\r\n URL = {http://www.ptidej.net/publications/documents/IWSC14.doc.pdf},\r\n PDF = {http://www.ptidej.net/publications/documents/IWSC14.ppt.pdf},\r\n ABSTRACT = {Ideally, any change that modifies the similar parts of a \r\n cloned code snippet should be propagated to all its duplicates. In \r\n practice however, consistent propagation of changes in clones does \r\n not always happen. Current evidence indicates that clone families \r\n have a 50\\NOchance of having consistent changes. This paper measures \r\n cloning and co-changes at file level as a proxy to assess the \r\n frequency of consistent changes. Given that changes to a clone group \r\n are not necessarily propagated in the same commit transaction (i.e., \r\n late propagations), our analysis uses macro co-changes instead of the \r\n traditional definition of co-changes. Macro changes group bursts of \r\n changes that are closer among themselves than to other changes, \r\n regardless of author or message. Then, macro co-changes are sets of \r\n files that change in the same macro changes. Each cloned file is \r\n tagged depending on whether any of the files with which it macro \r\n co-changes is cloned with it (during the macro change) or not. \r\n Contrary to previous results, we discovered that most of the cloned \r\n files macro co-change \\emph{only} with files with which they share \r\n clones. Thus providing evidence that macro changes are appropriate to \r\n study the conjecture of clones requiring co-changes, and indicating \r\n that consistent changes might be the norm in cloned code.}\r\n}\r\n\r\n","author_short":["Lozano, A.","Jaafar, F.","Mens, K.","Gu�h�neuc, Y."],"editor_short":["G�de, N.","Higo, Y."],"key":"Lozano14-IWSC-ClonesMacroCochanges","id":"Lozano14-IWSC-ClonesMacroCochanges","bibbaseid":"lozano-jaafar-mens-guhneuc-clonesandmacrocochanges-2014","role":"author","urls":{"Paper":"http://www.ptidej.net/publications/documents/IWSC14.doc.pdf"},"keyword":["Topic: Evolution patterns","Venue: IWSC"],"metadata":{"authorlinks":{"gu�h�neuc, y":"https://bibbase.org/show?bib=http%3A%2F%2Fwww.yann-gael.gueheneuc.net%2FWork%2FPublications%2FBiblio%2Fcomplete-bibliography.bib&msg=embed","guéhéneuc, y":"https://bibbase.org/show?bib=http://www.yann-gael.gueheneuc.net/Work/BibBase/guehene%20(automatically%20cleaned).bib"}},"downloads":0},"search_terms":["clones","macro","changes","lozano","jaafar","mens","gu�h�neuc"],"keywords":["topic: evolution patterns","venue: iwsc"],"authorIDs":["AfJhKcg96muyPdu7S","xkviMnkrGBneANvMr"],"dataSources":["Sed98LbBeGaXxenrM","8vn5MSGYWB4fAx9Z4"]}