Get 20M+ Full-Text Papers For Less Than $1.50/day. Start a 14-Day Trial for You or Your Team.

Learn More →

The need and techniques to obliterate control languages

The need and techniques to obliterate control languages Control language functions have greatly increased in recent times. Much of the increase is due to the fact that as new facilities were developed in operating systems no corresponding specifications were added to common programming languages. Programming languages did have statements that interfaced with input/output systems; these were also used to address problems of file and database management, as well as transfer of data between successive program segments. Unfortunately the control languages that took on the control and data flow specifications developed in an ad hoc fashion with little concern for intersystem consistency. Their syntax is frequently infantile and many specifications are set by local default conditions. The result is that control languages present one of the major stumbling blocks in programming and severelyhinder transferability of programs. http://www.deepdyve.com/assets/images/DeepDyve-Logo-lg.png ACM SIGPLAN Notices Association for Computing Machinery

The need and techniques to obliterate control languages

ACM SIGPLAN Notices , Volume 8 (9) – Sep 1, 1973

Loading next page...
 
/lp/association-for-computing-machinery/the-need-and-techniques-to-obliterate-control-languages-Vj3ES08oSk

References (3)

  • Compiler -Gary Breitbard The ACME (1968)

    358

  • Computer An Advanced (1968)

    B1

  • Computer An Advanced (1967)

    497

Publisher
Association for Computing Machinery
Copyright
Copyright © 1973 by ACM Inc.
ISSN
0362-1340
DOI
10.1145/390014.808304
Publisher site
See Article on Publisher Site

Abstract

Control language functions have greatly increased in recent times. Much of the increase is due to the fact that as new facilities were developed in operating systems no corresponding specifications were added to common programming languages. Programming languages did have statements that interfaced with input/output systems; these were also used to address problems of file and database management, as well as transfer of data between successive program segments. Unfortunately the control languages that took on the control and data flow specifications developed in an ad hoc fashion with little concern for intersystem consistency. Their syntax is frequently infantile and many specifications are set by local default conditions. The result is that control languages present one of the major stumbling blocks in programming and severelyhinder transferability of programs.

Journal

ACM SIGPLAN NoticesAssociation for Computing Machinery

Published: Sep 1, 1973

There are no references for this article.