Erik Hilsdale

dblp:42/2999 · DBLP profile ↗
← Back
2ranked-venue papers
0as first author
0since 2021 · last 2001
—ORCID · none

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

Software engineering, systems software and programming languages · 2

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
Requirements engineering and software design · 56% Programming languages and type systems · 44%

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

TopicWeightPapersLastEvidence papers
Programming languages and type systems
aspect-oriented programming
0.012001
Aspect-oriented programming · ESEC / SIGSOFT FSE 2001
Requirements engineering and software design
separation of concerns
0.012001
Aspect-oriented programming · ESEC / SIGSOFT FSE 2001
Requirements engineering and software design › separation of concerns
crosscutting concerns
0.012001
Aspect-oriented programming · ESEC / SIGSOFT FSE 2001

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

aspectj · 0.0aspectc · 0.0
YearPublicationVenuePosition
2001 An Overview of AspectJ
Gregor Kiczales, Erik Hilsdale, Jim Hugunin, Mik Kersten, Jeffrey Palm, William G. Griswold
ECOOP2
2001 Aspect-oriented programming
abstract
Aspect-oriented programming (AOP) is a technique for improving separation of concerns in software design and implementation. AOP works by providing explicit mechanisms for capturing the structure of crosscutting concerns. This tutorial shows how to use AOP to implement crosscutting conerns in a concise modular way. It works with AspectJ, a seamless aspect-oriented extension to the Java(tm) programming language, and with AspectC, an aspect-oriented extension to C in the style of AspectJ. It also includes a description of their underlying model, in terms of which a wide range of AOP languages can be understood.
Gregor Kiczales, Erik Hilsdale
ESEC / SIGSOFT FSE2