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

C. J. Stephenson

dblp:63/4810 · DBLP profile ↗
← Back
2ranked-venue papers
2as first author
0since 2021 · last 1983
—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
2 papers
Operating systems · 94% Programming languages and type systems · 6%

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

TopicWeightPapersLastEvidence papers
Operating systems › resource management › memory management
dynamic memory allocation
0.011983
Fast Fits · SOSP 1983
Operating systems › operating system interface
command language
0.011973
On the Structure and Control of Commands · SOSP 1973
Programming languages and type systems
language design
0.011973
On the Structure and Control of Commands · SOSP 1973
YearPublicationVenuePosition
1983 Fast Fits
C. J. Stephenson
SOSP1
1973 On the Structure and Control of Commands
abstract
An interactive command language, with its underlying data, defines a command environment. In general a command environment supports a number of commands which once issued perform non-interactively, and which when finished leave the old command environment in control. It also supports some special commands which move to other command environments, after which commands are interpreted according to a different set of rules.
C. J. Stephenson
SOSP1