The design of the REXX language
ACM SIGPLAN Notices
A software methodology for building interactive tools
ICSE '81 Proceedings of the 5th international conference on Software engineering
A high-level programming and command language
Proceedings of the 1983 ACM SIGPLAN symposium on Programming language issues in software systems
An introduction to the Programmer's Workbench
ICSE '76 Proceedings of the 2nd international conference on Software engineering
DAC '82 Proceedings of the 19th Design Automation Conference
Languages, Levels, Libraries, and Longevity
Queue - Programming Languages
A new object-oriented programming language: sh
USTC'94 Proceedings of the USENIX Summer 1994 Technical Conference on USENIX Summer 1994 Technical Conference - Volume 1
A prototyping environment for real-time graphics
AFIPS '84 Proceedings of the July 9-12, 1984, national computer conference and exposition
The design of the REXX language
IBM Systems Journal
| Hi-index | 0.00 |
The command language for the Programmer's Workbench (PWB) utilizes an extended version of the standard UNIX shell program, plus commands designed mainly for use within shell procedures (command files). Modifications have been aimed at improving the use of the shell by large programming groups, and making it even more convenient to use as a high-level programming language. In line with the philosophy of much existing UNIX software, an attempt has been made to add new features only when they are shown necessary by actual user experience in order to avoid contaminating a compact, elegant system through “creeping featurism.” By utilizing the shell as a programming language, PWB users have been able to eliminate a great deal of the programming drudgery that often accompanies a large project. Many manual procedures have been quickly, cheaply, and conveniently automated. Because it is so easy to create and use shell procedures, each separate project has tended to customize the general PWB environment into one tailored to its own requirements, organizational structure, and terminology. A summary is given of the usage patterns revealed by a survey of 1,725 existing shell procedures.