Assessing textual source code comparison: split or unified?

dc.contributor.authorAlejandra Cossio Chavalier
dc.contributor.authorJuan Pablo Sandoval Alcocer
dc.contributor.authorAlexandre Bergel
dc.coverage.spatialBolivia
dc.date.accessioned2026-03-22T16:21:34Z
dc.date.available2026-03-22T16:21:34Z
dc.date.issued2020
dc.descriptionCitaciones: 1
dc.description.abstractEvaluating source code differences is an important task in software engineering. Unified and split are two popular textual representations supported by clients for source code management. Whether these representations differ in supporting source code commit assessment is still unknown, despite its ubiquity in software production environments.
dc.identifier.doi10.1145/3397537.3398471
dc.identifier.urihttps://doi.org/10.1145/3397537.3398471
dc.identifier.urihttps://andeanlibrary.org/handle/123456789/57772
dc.language.isoen
dc.sourceUniversidad Católica Bolivia San Pablo
dc.subjectCommit
dc.subjectComputer science
dc.subjectSource code
dc.subjectCode (set theory)
dc.subjectKPI-driven code analysis
dc.subjectTask (project management)
dc.subjectStatic program analysis
dc.subjectCode review
dc.subjectProgramming language
dc.subjectSoftware
dc.titleAssessing textual source code comparison: split or unified?
dc.typearticle

Files