Many software systems contained cloned code, i.e., segments of code that are highly similar to each other, typically because one has been copied from the other, and then possibly modified. In some contexts, clones are of interest because they are targets for refactoring. This paper summarizes the results of a working session in which the problems of merely managing clones that are already known to exist. Six key issues in the space are briefly reviewed, and open questions raised in the working session are listed.
@InProceedings{kontogiannis:DagSemProc.06301.9, author = {Kontogiannis, Kostas}, title = {{Managing Known Clones: Issues and Open Questions}}, booktitle = {Duplication, Redundancy, and Similarity in Software}, pages = {1--5}, series = {Dagstuhl Seminar Proceedings (DagSemProc)}, ISSN = {1862-4405}, year = {2007}, volume = {6301}, editor = {Rainer Koschke and Ettore Merlo and Andrew Walenstein}, publisher = {Schloss Dagstuhl -- Leibniz-Zentrum f{\"u}r Informatik}, address = {Dagstuhl, Germany}, URL = {https://drops.dagstuhl.de/entities/document/10.4230/DagSemProc.06301.9}, URN = {urn:nbn:de:0030-drops-9679}, doi = {10.4230/DagSemProc.06301.9}, annote = {Keywords: Code clone, software evolution, change management, code visualization, redundancy, metamodels, software management environments} }
Feedback for Dagstuhl Publishing