12th Working Conference on Reverse Engineering (WCRE'05) 2005
DOI: 10.1109/wcre.2005.33
|View full text |Cite
|
Sign up to set email alerts
|

When functions change their names: automatic detection of origin relationships

Abstract: It is a common understanding that identifying the

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2008
2008
2024
2024

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 30 publications
(2 citation statements)
references
References 18 publications
0
2
0
Order By: Relevance
“…Visibility modifier, return type, but exception throws are not considered. According to [15], since a function's signature does not change frequently, the signature pattern can be used in determining similarity between methods. • Method Spread (MSP).…”
Section: Phase-2 Metrics Formulation and Clusteringmentioning
confidence: 99%
“…Visibility modifier, return type, but exception throws are not considered. According to [15], since a function's signature does not change frequently, the signature pattern can be used in determining similarity between methods. • Method Spread (MSP).…”
Section: Phase-2 Metrics Formulation and Clusteringmentioning
confidence: 99%
“…Another line of research related to MkDiff is origin analysis ( 39), ( 40), (41). Kim et al (40) use various similarity factors for matching entities from one version to another, including methods' names/signatures, caller/callee sets, texts, and complexity metrics. To match two methods in two versions, BEAGLE (41) first computes internal similarity based on the metrics such as Cyclomatic, S-, and D-Complexity.…”
Section: Related Workmentioning
confidence: 99%