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

Nicolas Graube

dblp:71/7023 · DBLP profile ↗
← Back
2ranked-venue papers
2as first author
0since 2021 · last 1989
—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 · 100%

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

TopicWeightPapersLastEvidence papers
Programming languages and type systems
inheritance
0.011989
Metaclass Compatibility · OOPSLA 1989
Programming languages and type systems › object-oriented programming
metaclasses
0.011989
Metaclass Compatibility · OOPSLA 1989
Programming languages and type systems › object-oriented programming
object-oriented language design
0.011989
Metaclass Compatibility · OOPSLA 1989
YearPublicationVenuePosition
1989 Metaclass Compatibility
abstract
Metaclasses provide control of object description, method compilation and more generally class behaviour. Consequently, they have been widely used in languages such as Smalltalk-80 or more recently CLOS by both users and implementers. Due to their powerful control of instances, careless inheritance of classes with different metaclasses can lead to unsound or inefficient implementations of instance methods. Using examples, we will pin-point these problems. Then we will introduce compatibility rules which need to be fulfilled by metaclasses of inherited classes in order to allow reasonable instance method description.
Nicolas Graube
OOPSLA1
1988 Reflexive Architecture: From ObjVLisp to CLOS
Nicolas Graube
ECOOP1