Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Workspace Development in APL

IP.com Disclosure Number: IPCOM000088695D
Original Publication Date: 1977-Jul-01
Included in the Prior Art Database: 2005-Mar-04
Document File: 2 page(s) / 78K

Publishing Venue

IBM

Related People

Burghard, KV: AUTHOR [+2]

Abstract

Described is a procedure that makes APL more useful in a program development environment. A program (BASE) is being developed, and the user's changes to the program (DELTA) are kept in separate workspaces.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 83% of the total text.

Page 1 of 2

Workspace Development in APL

Described is a procedure that makes APL more useful in a program development environment. A program (BASE) is being developed, and the user's changes to the program (DELTA) are kept in separate workspaces.

At the beginning of a session a function (UPMODEL) is invoked which loads and saves a workspace MYBASE with the BASE workspace and copies in the user's DELTA workspace. During the session, as changes are verified, the user may invoke a function (REVCOPY) which copies specified objects from MYBASE and specified changes to the BASE into the DELTA workspace, and then restores MYBASE. The syntax is: REVCOPY A where A is a character matrix of the names of functions or variables to be copied to DELTA. (A scalar or vector will work for single items to be copied.) Flow diagrams for UPMODEL and REVCOPY are provided in Figs. 1 and 3, respectively.

One or more independently tested sets of changes (DELTA workspaces) may periodically be merged into the BASE to form a new BASE workspace. If used in a top-down implementation of a program, this allows individual parts of the program to be tested separately and integrated easily when completed. Fixes to high level modules can be tested thoroughly before being placed into the BASE.

Once a user has had his DELTA merged into the BASE, he may begin his session by using a function (LOADMOD) which creates an empty DELTA and loads a copy of the BASE workspace, and names it MYBASE. A flow diagram for LOADMO...