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

Donal Lafferty

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

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

Software engineering, systems software and programming languages · 1 · 1 first-author

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
Programming languages and type systems · 77% Compilers and program optimization · 23%

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

TopicWeightPapersLastEvidence papers
Programming languages and type systems
aspect-oriented programming
0.012003
Language-independent aspect-oriented programming · OOPSLA 2003

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

common language infrastructure · 0.0XML aspect binding specification · 0.0
YearPublicationVenuePosition
2003 Language-independent aspect-oriented programming
abstract
The term aspect-oriented programming (AOP) has come to describe\nthe set of programming mechanisms developed specifically to\nexpress crosscutting concerns. Since crosscutting concerns cannot\nbe properly modularized within object-oriented programming, they\nare expressed as aspects and are composed, or woven, with\ntraditionally encapsulated functionality referred to as components.\nMany AOP models exist, but their implementations are typically\ncoupled with a single language. To allow weaving of existing\ncomponents with aspects written in the language of choice, AOP\nrequires a language-independent tool.\nThis paper presents Weave.NET, a load-time weaver that allows\naspects and components to be written in a variety of languages and\nfreely intermixed. Weave.NET relies on XML to specify aspect\nbindings and standardized Common Language Infrastructure to\navoid coupling aspects or components with a particular language.\nBy demonstrating language-independence, Weave.NET provides a\nmigration path to the AOP paradigm by preserving existing\ndeveloper knowledge, tools, and software components. The tool?s\ncapabilities are demonstrated with logging aspects written in and\napplied to Visual Basic and C# components.
Donal Lafferty, Vinny Cahill
OOPSLA1