System Formulation and APL Shared Variables

Lathwell, R. H.

doi:10.1147/rd.174.0353

Cited by 33 publications

(4 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…11 The consensus was that this approach was the one least likely to compromise the integrity and generality of the language, as it avoided the introduction of special functions just for manipulating files. 11 The consensus was that this approach was the one least likely to compromise the integrity and generality of the language, as it avoided the introduction of special functions just for manipulating files.…”

Section: Falkoffmentioning

confidence: 99%

The IBM family of APL systems

Falkoff

1991

IBM Syst. J.

View full text Add to dashboard Cite

The developmental history of IBM subfamilies of APL systems is traced in this paper, focusing on the inter-relationships among them and the. methods of implementation used by the venous groups Involved. The language Itself, and.the way Its evolution was managed, are also considered as factors Influencing the development process. A chart Is Included that illustrates the evolution of mainframe and small machine programming products supporting APL, beginning in 1964 up to the present time.

show abstract

Section: Falkoffmentioning

confidence: 99%

The IBM family of APL systems

Falkoff

1991

IBM Syst. J.

View full text Add to dashboard Cite

show abstract

“…In 1970 R. H. Lathwell proposed what was to become the basis of a general solution to many systems problems of APL\360, a shared variable processor [30] which implemented the shared variable scheme of communication among processors. This work culminated in the APLSV System [31] which became generally available in 1973.…”

Section: Systemsmentioning

confidence: 99%

The evolution of APL

Falkoff¹,

Iverson²

1978

History of Programming Languages

View full text Add to dashboard Cite

This paper is a discussion of the evolution of the APL language, and it treats implementations and applications only to the extent that they appear to have exercised a major influence on that evolution. Other sources of historical information are cited in References 1-3; in particular, The Design of APL [1] provides supplementary detail on the reasons behind many of the design decisions made in the development of the language. Readers requiring background on the current definition of the language should consult APL Language [4].Although we have attempted to confirm our recollections by reference to written documents and to the memories of our colleagues, this remains a personal view which the reader should perhaps supplement by consulting the references provided. In particular, much information about individual contributions will be found in the Appendix to The Design of APL [1], and in the Acknowledgments in A Programming Language [10] and in APL\360 User's Manual [23]. Because Reference 23 may no longer be readily available, the acknowledgments from it are reprinted in Appendix A.McDonnell's recent paper on the development of the notation for the circular functions [5] shows that the detailed evolution of any one facet of the language can be both interesting and illuminating. Too much detail in the present paper would, however, tend to obscure the main points, and we have therefore limited ourselves to one such example. We can only hope that other contributors will publish their views on the detailed developments of other facets of the language, and on the development of various applications of it.The development of the language was first begun by Iverson as a tool for describing and HISTORY OF PROGRAMMING LANGUAGES

show abstract

“…Instead of providing communication functions, as such, APL provides functions for establishing and managing interfaces composed of shared variables (2,3).…”

Section: A General Shared Variable Facilitymentioning

confidence: 99%

Some implications of shared variables

Falkoff¹

1976

Proceedings of the Eighth International Conference on APL - APL '76

View full text Add to dashboard Cite

Recognition ofshared variables as the fundamental means of communication between concurrently operating processes has important implications for the design of systems and programming languages.As a consequence, current APL systems, such as APLSV, embody two shared variable facilities: one for establishing temporary interfaces between system components, and the other one for defining parts of the permanent interface between an APL program and the underlying processor.These are treated in depth in this paper.More general implications for language and system design, system programming, and system performance are briefly noted.It is observed, for example, that languages that attempt to communicate with the environment without the explicit use of shared variables do not have a true communication facility, and therefore tend to absorb more and more of the environment within their own formal structure.

show abstract

System Formulation and APL Shared Variables

Cited by 33 publications

References 2 publications

The IBM family of APL systems

The IBM family of APL systems

The evolution of APL

Some implications of shared variables

Contact Info

Product

Resources

About