NDLI: System commands:an APL backwater revisited

Please wait, while we are loading the content...

Volume 15, Issue 4, May 12, 1985

Array oriented exception handling

An SQL interface for VS APL

The APL 90 project

Freestyle graphics with APL

Dataflow analysis in APL

Compiling APL for parallel execution on an FFP machine

The graphical kernal system—an opportunity for APL

APL and GDDM (tutorial)

Design of APL (tutorial)

System commands

An integrated business application architecture

Software publishing and the software developer

Integrating ordinary type and many languages with the APL alphabet and keyboard

Efficiency in the APL environment—a full arsenal for attacking CPU hogs

APL teaching bugs

APL and robotics

Artificial intelligence development aids (AIDA)

Improving APL performance with custom written auxiliary processors

Control of structure and evaluation

Corporate application of APL—case studies (panel)

APL graphics products (panel)

Writing interpreters (panel)

APLIM—applied linear interactive models

Extended shared-variable sessions

Using dimensions to represent attributes

Structural experiments with arrays of functions

Operators for program control

Operators for recursion

The use of APL versus other languages—a six year trend analysis

Tadpoles and frogs

Lotus 1-2-3 for mainframes (bringing a product to market)

An APL database system for R&D laboratories

Mortgage insurance

Mathematics education through the perspective of rationalized APL

An introduction to STSC's APL compiler

A group of APL functions for computer-assisted instruction

The intelligent approach to teaching arithmetic

Commercial applications (panel)

Promoting APL (panel)

Developing auxiliary processors (tutorial)

N-dimensional geometry using APL2

An APL production environment

Inside the APL2 workspace

APLGRAPH—how to develop graphics software without really trying

An APL based relational data management language using SYSTEM R as data server

APL microcomputer products (panel)

APL programming standards (panel)

Volume 15, Issue 3, March 1985

Volume 15, Issue 2, Dec. 1984

Volume 15, Issue 1, Sept. 1984

System commands:an APL backwater revisited

Content Provider	ACM Digital Library
Author	Berry, Michael J. A.
Abstract	System commands have always had a very important role in, or, more accurately, just outside, the APL language. They are the pidgin dialect which provides communication between the clean, abstract world of pure APL and the often messy environment of the APL system which allows APL programs to be executed. Despite their importance in the development and use of all APL applications, very little attention has been paid to them. They remain, in contrast to APL itself, ineffectual, irregular, and inconsistent. They have no regular syntax and return no usable result. There are two possible ways to deal with this situation. Get rid of them, or make them better.To date, most APL systems have been gradually implementing the first approach. One by one, system commands have been superseded by system functions and variables which do approximately the same thing. In the case of system variables such as □IO and □RL whose values effect the actual results of calculations as implicit arguments, this change has properly moved the ability to set these parameters into the province of the language itself. In the case of the system functions, however, the move has blurred the useful distinction between the language and the host environment and introduced a most unattractive collection of obscure English words and abbreviations into a previously ideographic language.By moving the English words out of APL and into the realm of system commands, we open up the possibility of having the actual words used be a function of some natural language selection facility such as □NLT in IBM's APL2.One of the problems with the □-function approach is that APL functions take data arguments and return data results. This is, of course, what allows them to be used in ever more complex expressions. Unfortunately, since the environmental constructs acted on by system functions are not data, the arguments and results of system functions often bear only slightly on the main action which is taken as a side effect.Another problem is that an APL function works within a certain name environment (workspace), and generally cannot affect things outside of that environment. As large applications increasingly tend to rely on cooperation between many different workspaces, the need to make extra-workspace adjustments to the environment has become apparent. This is especially true in Analogic APL which is designed to facilitate the sharing of both functions and variables between workspaces.Starting a brand new implementation of APL is a great opportunity. We at Analogic decided to take advantage of it by providing a better environment for our favorite language to run in. Our approach was to leave the language proper alone (Analogic is committed to strict adherence to the ISO APL standard), but to rethink the way that APL applications interact with their environment. To take advantage of these enhancements, an applications programmer must set up a variety of links between different workspaces or name contexts. Usually, this only needs to be done once at the time an application is put together. The exact mechanism, called threaded workspaces, is described elsewhere [1]. The important points for this discussion are that the actions generally need not be dynamic and that there are many variations in the details of the connections.We decided that system functions were not the answer. Doing as many things as we envisioned by using system functions would have entitled either an unacceptably large number of confusingly named &squarel-functions (like the 135 found in STSC APL*PLUS/PC) or unacceptably obscure arguments to a smaller number of □-functions (like the left arguments of □WS and □FD in Sharp APL).System commands, many of which are already required by the ISO standard, can provide the answer so long as they are given a regular and self-documenting syntax, and the universe of names visible to any command is expanded to include names in workspaces other than the one in which the command is invoked.It should be understood that Analogic APL is a work in progress. The ideas expressed here reflect the current state of the specification of Analogic APL. Details such as the names of individual fields are likely to change as we the implementation progresses and we gather experience.
Starting Page	49
Ending Page	51
Page Count	3
File Format	PDF
ISSN	01636006
DOI	10.1145/255315.255338
Journal	ACM SIGAPL APL Quote Quad (APLQ)
Volume Number	15
Issue Number	4
Language	English
Publisher	Association for Computing Machinery (ACM)
Publisher Date	1988-12-01
Publisher Place	New York
Access Restriction	One Nation One Subscription (ONOS)
Content Type	Text
Resource Type	Article

Central Library (ISO-9001:2015 Certified)
Indian Institute of Technology Kharagpur
Kharagpur, West Bengal, India | PIN - 721302

See location in the Map
03222 282435
Mail: support@ndl.gov.in

Sl.	Authority	Responsibilities	Communication Details
1	Ministry of Education (GoI), Department of Higher Education	Sanctioning Authority	https://www.education.gov.in/ict-initiatives
2	Indian Institute of Technology Kharagpur	Host Institute of the Project: The host institute of the project is responsible for providing infrastructure support and hosting the project	https://www.iitkgp.ac.in
3	National Digital Library of India Office, Indian Institute of Technology Kharagpur	The administrative and infrastructural headquarters of the project	Dr. B. Sutradhar bsutra@ndl.gov.in
4	Project PI / Joint PI	Principal Investigator and Joint Principal Investigators of the project	Dr. B. Sutradhar bsutra@ndl.gov.in Prof. Saswat Chakrabarti will be added soon
5	Website/Portal (Helpdesk)	Queries regarding NDLI and its services	support@ndl.gov.in
6	Contents and Copyright Issues	Queries related to content curation and copyright issues	content@ndl.gov.in
7	National Digital Library of India Club (NDLI Club)	Queries related to NDLI Club formation, support, user awareness program, seminar/symposium, collaboration, social media, promotion, and outreach	clubsupport@ndl.gov.in
8	Digital Preservation Centre (DPC)	Assistance with digitizing and archiving copyright-free printed books	dpc@ndl.gov.in
9	IDR Setup or Support	Queries related to establishment and support of Institutional Digital Repository (IDR) and IDR workshops	idr@ndl.gov.in