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 8<sup>th</sup> 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% chance 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{\"e}l Gu{\'e}h{\'e}neuc},
title = {Clones and Macro Co-changes},
booktitle = {Proceedings of the 8<sup>{th}</sup> International Workshop on Software Clones ({IWSC})},
year = {2014},
month = {February},
editor = {Nils G{\"o}de and Yoshiki Higo},
publisher = {Electronic Communications of the EASST},
note = {15 pages.},
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\% chance 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.},
grant = {NSERC DG and CRC on Software Patterns},
keywords = {Evolution patterns ; IWSC},
kind = {MIADR},
language = {english},
url = {http://www.ptidej.net/publications/documents/IWSC14.doc.pdf},
pdf = {http://www.ptidej.net/publications/documents/IWSC14.ppt.pdf}
}
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/BibBase/guehene (automatically cleaned).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":[]}],"title":"Clones and Macro Co-changes","booktitle":"Proceedings of the 8<sup>th</sup> International Workshop on Software Clones (IWSC)","year":"2014","month":"February","editor":[{"firstnames":["Nils"],"propositions":[],"lastnames":["Göde"],"suffixes":[]},{"firstnames":["Yoshiki"],"propositions":[],"lastnames":["Higo"],"suffixes":[]}],"publisher":"Electronic Communications of the EASST","note":"15 pages.","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% chance 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.","grant":"NSERC DG and CRC on Software Patterns","keywords":"Evolution patterns ; IWSC","kind":"MIADR","language":"english","url":"http://www.ptidej.net/publications/documents/IWSC14.doc.pdf","pdf":"http://www.ptidej.net/publications/documents/IWSC14.ppt.pdf","bibtex":"@INPROCEEDINGS{Lozano14-IWSC-ClonesMacroCochanges,\n author = {Angela Lozano and Fehmi Jaafar and Kim Mens and Yann-Ga{\\\"e}l Gu{\\'e}h{\\'e}neuc},\n title = {Clones and Macro Co-changes},\n booktitle = {Proceedings of the 8<sup>{th}</sup> International Workshop on Software Clones ({IWSC})},\n year = {2014},\n month = {February},\n editor = {Nils G{\\\"o}de and Yoshiki Higo},\n publisher = {Electronic Communications of the EASST},\n note = {15 pages.},\n 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\\% chance 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.},\n grant = {NSERC DG and CRC on Software Patterns},\n keywords = {Evolution patterns ; IWSC},\n kind = {MIADR},\n language = {english},\n url = {http://www.ptidej.net/publications/documents/IWSC14.doc.pdf},\n pdf = {http://www.ptidej.net/publications/documents/IWSC14.ppt.pdf}\n}\n\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":["Evolution patterns ; 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,"html":""},"search_terms":["clones","macro","changes","lozano","jaafar","mens","guéhéneuc"],"keywords":["evolution patterns ; iwsc"],"authorIDs":["AfJhKcg96muyPdu7S","xkviMnkrGBneANvMr"],"dataSources":["Sed98LbBeGaXxenrM","8vn5MSGYWB4fAx9Z4"]}