Contact us Heritage collections Image license terms
HOME ACL Associates Technology Literature Applications Society Software revisited
Further reading □ OverviewNo.1No.2No.3No.4No.5No.8No.9No.11No.12No.13No.14No.15No.17No.19No.21No.22No.23No.24No.25No.26No.27No.28No.29No.30No.31No.32No.33No.37No.38No.39No.40No.41No.43No.44No.45No.46No.47No.48No.49No.50No.51No.52
ACD C&A INF CCD CISD Archives Contact us Heritage archives Image license terms

Search

   
ACLLiteratureProgress ReportsSPROGS Papers
ACLLiteratureProgress ReportsSPROGS Papers
ACL ACD C&A INF CCD CISD Archives
Further reading

Overview
No.1
No.2
No.3
No.4
No.5
No.8
No.9
No.11
No.12
No.13
No.14
No.15
No.17
No.19
No.21
No.22
No.23
No.24
No.25
No.26
No.27
No.28
No.29
No.30
No.31
No.32
No.33
No.37
No.38
No.39
No.40
No.41
No.43
No.44
No.45
No.46
No.47
No.48
No.49
No.50
No.51
No.52

SPROGS Paper No 39: SPROGS Version 2 - What Should be Included

R E Thomas

November 28 1973

INTRODUCTION

It is intended to issue a second version of the system to users in December. The manual is currently being retyped. However, there are a number of points to be raised.

(1) Should a 'glossy' manual be issued for this version? Such a manual will be produced by a printer with smart cover, and it will be easy to obtain copies (using the Xerox for many copies takes a long time). However, it is not worth the extra expense if major changes are likely in the near future.

(2) Should we aim to include any more facilities in Version 2 before it is released, particularly with regard to point 1 above.

To assist in such decisions, the following is a list of jobs which have still to be completed (among others).

LARGE JOBS

These are defined as non-trivial additions, on which no work has yet started.

(1) Local variables and arguments

The method of approach has been defined, but the coding and testing is likely to take 2-3 months.

(2) Advance repeat

An automatic repetition of frames could be done by using temporary storage in the file store. Such a facility, however, may lead to major changes in the code.

(3) Dotted lines

Since the early discussions on STROKE, this problem has received no further attention. STROKE itself, if implemented, is likely to prove difficult.

(4) Data mode

With the preprocessor already in existence, a certain amount of data definition has been done, but it relies heavily on the form required for use by PDP15, and the coding may be difficult.

(5) PDP15

With the introduction of RSX3, there is likely to be a delay in the release of software on the PDP15 for the general user, maybe as late as Spring 1974.

(6) User-oriented routines

Little extra work has been done to provide extra facilities in conjunction with histograms, contours etc. A usable system ought to include these frills.

JOBS BEING DEVELOPED·

There are a number of jobs for which work is in hand, and which are nearing completion, but which have yet to be included.

(1) THICK

Routines to provide variable line thickness exist but no attempt has yet been made to incorporate them.

(2) Suffix/superfix

Code which follows the GROATS plan has been written to provide the necessary scaling and off-setting.

(3) Circle/ellipse scissoring

Routines to scissor a line for circular and elliptic areas have been tested, but no attempt to include them into the regions has been made.

Although not strictly started yet, the inclusion of COLOUR is fairly simple. It has been given as thesis task to David Ralphs, and hence is nearly finished.

(5) Hewlett-Packard plotter

Routines have been written to handle this device. However, they cannot be completely tested, or included in DVOUT, until a device is available.

(6) STCHSZ, GVCHSZ

These routines give scaling information for characters so that automation TEXPAN factors can be generated. Again, these have yet to be fully integrated.

SMALL JOBS

The following jobs have been defined, and their implementation seems fairly simple, but no work has begun.

(1) IFS

One-shot WHILE.

(2) STSQLS

Start sequence list without adding a file.

(3) AIR

Same as AR, but with autoincrementing on the third index variable.

(4) SPSQLS

To be effective outside a file definition, so that suspended items can be added to the sequence list.

(5) ADSQLL

To have a bit set to cause automatic repetition of the named file.

(5) User display routines

This can easily be done by providing some extra locations in the display name table, extra calls to null routines in OBEY and a routine to set up the display name table. A user would write his own display routine and use one of the dummy routine names in OBEY for the execution part.

(7) File deletion

This needs changes to IFPOS to make allowances during the hash search.

(8) Index variable deletion

This needs changes as above to INPOS.

MEDIUM JOBS

There are two jobs which have been designed, but not started, which could take a significant amount of work, although not sufficient to warrant being described as large jobs.

(1) NULL packing

This involves the packing of null files so that only the arguments need to be stored. Such a file will have to be read using file length to detect the end, since no FIDF will be present.

(2) Argument checking during file packing

Currently no check is kept on the arguments to see if they really are integral, or whether they really do fit in 12 or 6 bits. Such checking would slow the packing of files considerably.

In addition to the above, the following two jobs must be done before the second release.

(1) Inclusion of spooling, which is being tested.

(2) Inclusion of owned tapes and the removal of RETAIN.

⇑ Top of page
© Chilton Computing and UKRI Science and Technology Facilities Council webmaster@chilton-computing.org.uk
Our thanks to UKRI Science and Technology Facilities Council for hosting this site