For example, a functional GUI for Khoros 1.1 is available for demo purposes. The AIPS shell interpreter can be thought of in terms of the Miriad 1.2 shell interpreter. The programmer however will never interact with a parameter through it's class interface. The purpose of these is to tell the task how to communicate with the user and it's environment, and give the user control over these items. Parameter names are to be found by minimum match, if so requested by the user.
Most programs are probably happy with a simple set of parameters, like a linear list.
We have discussed hierarchical keywords and in Section 1.3 a few thoughts are expressed. All input as well as output is controlled by the user interface. The Astronomer has a varying degree of control over how and where input and output occurs. In the command line interface system control occurs through a small number of system parameters, which can be preset by environment variables, supplied as if they were parameters on the command line, or both. In addition, a Version and Usage string should be supplied to the user interface.