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.

David Kitchin

dblp:31/4342 · DBLP profile ↗
← Back
5ranked-venue papers
2as first author
0since 2021 · last 2016
—ORCID · none

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

Software engineering, systems software and programming languages · 3 · 1 first-authorTheory of computation · 3 · 2 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 · 100%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 77% Performance modeling and evaluation · 23%

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

TopicWeightPapersLastEvidence papers
Programming languages and type systems › concurrent programming languages
concurrent object-oriented programming
0.212016
OrcO: a concurrency-first approach to objects · OOPSLA 2016
Distributed systems › distributed algorithms
logical clocks
0.112008
Simulation, Orchestration and Logical Clocks · FM 2008
Programming languages and type systems
object-oriented programming
0.112016
OrcO: a concurrency-first approach to objects · OOPSLA 2016
Performance modeling and evaluation
simulation
0.012008
Simulation, Orchestration and Logical Clocks · FM 2008
YearPublicationVenuePosition
2016 OrcO: a concurrency-first approach to objects
abstract
The majority of modern programming languages provide concurrency and object-orientation in some form. However, object-oriented concurrency remains cumbersome in many situations. We introduce the language OrcO, Orc with concurrent Objects, which enables a flexible style of concurrent object-oriented programming. OrcO extends the Orc programming language by adding abstractions for programming-in-the-large; namely objects, classes, and inheritance. OrcO objects are designed to be orthogonal to concurrency, allowing the concurrent structure and object structure of a program to evolve independently. This paper describes OrcO's goals and design and provides examples of how OrcO can be used to deftly handle events, object management, and object composition.
Arthur Michener Peters, David Kitchin, John A. Thywissen, William R. Cook
OOPSLA2
2008 Simulation, Orchestration and Logical Clocks
David Kitchin, Evan Powell, Jayadev Misra
FM1
2008 A timed semantics of Orc
Ian Wehrman, David Kitchin, William R. Cook, Jayadev Misra
Theor. Comput. Sci.2
2007 Safe composition of product lines
abstract
Programs of a software product line can be synthesized by composing modules that implement features. Besides high-level domain constraints that govern the compatibility of features, there are also low-level implementation constraints: a feature module can reference elements that are defined in other feature modules. Safe composition is the guarantee that all programs in a product line are type safe: i.e., absent of references to undefined elements (such as classes, methods, and variables). We show how safe composition properties can be verified for AHEAD product lines using feature models and SAT solvers.
Sahil Thaker, Don S. Batory, David Kitchin, William R. Cook
GPCE3
2006 A Language for Task Orchestration and Its Semantic Properties
David Kitchin, William R. Cook, Jayadev Misra
CONCUR1