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.

Jay Almarode

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

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

Software engineering, systems software and programming languages · 2 · 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 · 94% Concurrent programming · 6%

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

TopicWeightPapersLastEvidence papers
Programming languages and type systems › object-oriented programming
delegation
0.011989
Rule-Based Delegation for Prototypes · OOPSLA 1989
Programming languages and type systems
inheritance
0.011989
Rule-Based Delegation for Prototypes · OOPSLA 1989
Programming languages and type systems › object-oriented programming
multiple inheritance
0.011989
Rule-Based Delegation for Prototypes · OOPSLA 1989
Programming languages and type systems
object-oriented programming
0.011989
Rule-Based Delegation for Prototypes · OOPSLA 1989
Programming languages and type systems › object-oriented programming
prototype-based languages
0.011989
Rule-Based Delegation for Prototypes · OOPSLA 1989
Concurrent programming
message passing
0.011989
Rule-Based Delegation for Prototypes · OOPSLA 1989

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

rule-based delegation · 0.0
YearPublicationVenuePosition
1991 Issues in the Design and Implementation of a Schema Designer for an OODBMS
Jay Almarode
ECOOP1
1989 Rule-Based Delegation for Prototypes
abstract
Arguments have been given recently for providing the functionality of prototypes in object-oriented languages. Prototypes allow more flexible sharing of code and data by delegating messages to parent objects without the rigid structure of a class hierarchy. Prototypes can implement classes, and delegation can be used to model both single and multiple inheritance. However, one drawback with delegation is the difficulty in enforcing the semantics that delegation is used to model. This paper proposes a novel mechanism to control the delegation of messages with rules. In this system, the delegation of messages is governed by a set of rules possessed by each object. Rules can be used to implement classical single inheritance and can implement various solutions to multiple inheritance. In addition, rules can be created dynamically to model application-specific semantics. This paper describes how rule-based delegation works and illustrates various rules for rule-based delegation that have been implemented.
Jay Almarode
OOPSLA1