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

Paul R. Kosinski

dblp:28/6274 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 1976
—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 · 87% Compilers and program optimization · 13%

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

TopicWeightPapersLastEvidence papers
Programming languages and type systems › language semantics
concurrent language semantics
0.011976
Mathematical Semantics and Data Flow Programming · POPL 1976
Programming languages and type systems › programming paradigms
dataflow language
0.011976
Mathematical Semantics and Data Flow Programming · POPL 1976
Compilers and program optimization › program transformation › program optimization
semantics-preserving optimization
0.011976
Mathematical Semantics and Data Flow Programming · POPL 1976

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

denotational semantics · 0.0
YearPublicationVenuePosition
1976 Mathematical Semantics and Data Flow Programming
abstract
A Data Flow program [1,2] is a flow-chart like network of operators which compute concurrently, dependent only on the availability of the data which flow along the paths. Each operator has only a local effect, transforming input data to output data. Although operators may exhibit memory and thus not be functional from an input to an output, all operators are functions from input sequences to output sequences. This plus the strong locality of effect allows mathematization of semantics more readily than traditional programming languages which are burdened with omnipresent storage and occasional GOTO's. This paper proves the semantic behavior of some elementary Data Flow programs and proves that certain optimization transformations preserve other behaviors.
Paul R. Kosinski
POPL1