Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Valentin Kostadinov

dblp:47/1913 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2002
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Program analysis · 61% Programming languages and type systems · 30% Software maintenance and evolution · 9%

Topics — the 4 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Program analysis › static analysis
pointer analysis
0.012002
Alias annotations for program understanding · OOPSLA 2002
Program analysis
static analysis
0.012002
Alias annotations for program understanding · OOPSLA 2002
Programming languages and type systems
type systems
0.012002
Alias annotations for program understanding · OOPSLA 2002
Software maintenance and evolution
program comprehension
0.012002
Alias annotations for program understanding · OOPSLA 2002

Methods — techniques the papers use, named apart from their topics

capability-based alias annotation · 0.0annotation inference · 0.0
YearPublicationVenuePosition
2002 Alias annotations for program understanding
abstract
One of the primary challenges in building and evolving large object-oriented systems is understanding aliasing between objects. Unexpected aliasing can lead to broken invariants, mistaken assumptions, security holes, and surprising side effects, all of which may lead to software defects and complicate software evolution.This paper presents AliasJava, a capability-based alias annotation system for Java that makes alias patterns explicit in the source code, enabling developers to reason more effectively about the interactions in a complex system. We describe our implementation, prove the soundness of the annotation system, and give an algorithm for automatically inferring alias annotations. Our experience suggests that the annotation system is practical, that annotation inference is efficient and yields appropriate annotations, and that the annotations can express important invariants of data structures and of software architectures.
Jonathan Aldrich, Valentin Kostadinov, Craig Chambers
OOPSLA2