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

John R. Mashey

dblp:78/4249 · DBLP profile ↗
← Back
5ranked-venue papers
3as first author
0since 2021 · last 1979
0000-0002-7065-4849ORCID · corroborated

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

Software engineering, systems software and programming languages · 4 · 2 first-authorHuman-computer interaction and ubiquitous computing · 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
2 papers
Operating systems · 50% Software maintenance and evolution · 50%

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

TopicWeightPapersLastEvidence papers
Operating systems › operating system interface
command language
0.011976
Using a Command Language as a High-Level Programming Language · ICSE 1976
Software maintenance and evolution
software documentation
0.011976
Documentation Tools and Techniques · ICSE 1976
YearPublicationVenuePosition
1979 The UNIX/TM Programming Environment
abstract
Abstract The UNIX UNIX is a trademark of Bell Laboratories. operating system provides an especially congenial programming environment, in which it is not only possible, but actually natural, to write programs quickly and well. Several characteristics of the UNIX system contribute to this desirable state of affairs. Files have no type or internal structure, so data produced by one program can be used by another without impediment. The basic system interface for input and output provides homogeneous treatment of files, I/O devices and programs, so programs need not care where their data comes from or goes to. The command interpreter makes it convenient to connect programs, by arranging for all data communication. Complex procedures are created not by writing large programs from scratch, but by interconnecting relatively small components. These programs are small and concentrate on single functions, and therefore are easy to build, understand, describe, and maintain. They form a high level toolkit whose existence causes programmers to view their work as the use and creation of tools, a viewpoint that encourages growth in place of reinvention. Tools interact in a limited number of ways, but can be used in many different combinations. Thus, an addition to the toolkit tends to improve the programming power of the user faster than it increases the complexity of interconnection and maintenance. Finally, tools are connected at a very high level by a powerful command language interpreter. The error‐prone and expensive process of program writing can often be avoided in favor of program‐using. In this paper we will present a variety of examples to illustrate this methodology, focusing on those aspects of the system and supporting software which make it possible.
Brian W. Kernighan, John R. Mashey
Softw. Pract. Exp.2
1976 An Introduction to the Programmer's Workbench
Ted A. Dolotta, John R. Mashey
ICSE2
1976 Using a Command Language as a High-Level Programming Language
John R. Mashey
ICSE1
1976 Documentation Tools and Techniques
John R. Mashey, D. W. Smith
ICSE1
1973 ASSIST: Three year's experience with a student-oriented assembler
abstract
ASSIST is a high-speed assembler/interpreter system for IBM System/360 and related computers. It is designed primarily for efficient processing of student jobs, and offers a number of educational features. ASSIST is now being used at a number of installations under widely varying circumstances. This paper analyzes the design process and decisions leading to ASSIST, concentrating on the factors felt to be most important to its usage. Implementation problems and experiences are noted, and conclusions drawn from them regarding the design of student job processors and desired operating system facilities to support them.
John R. Mashey
SIGCSE1