DataMuseum.dk

Presents historical artifacts from the history of:

RC4000/8000/9000

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about RC4000/8000/9000

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - metrics - download

⟦a8f86e0be⟧ TextFile

    Length: 7680 (0x1e00)
    Types: TextFile
    Names: »guideinp«

Derivation

└─⟦621cfb9a2⟧ Bits:30002817 RC8000 Dump tape fra HCØ.  Detaljer om "HC8000" projekt.
    └─⟦0364f57e3⟧ 
        └─⟦8c6b0f8fa⟧ »cdes« 
└─⟦667bb35d6⟧ Bits:30007480 RC8000 Dump tape fra HCØ.
    └─⟦4334b4c0b⟧ 
        └─⟦8c6b0f8fa⟧ »cdes« 
            └─⟦this⟧ 

TextFile

*pl 297,18,250,4,3**pn 0,0*
*lw 170**ps 0**sj*
H. C. Ørsted Institute
Computer Department
Universitetsparken 5
DK-2100 København Ø
*nl4*
*ct*
Guideline for description of

algol8 procedures for the HCØ RC8000 algol8

procedure library

and

programs for the HCØ RC8000

program library
"guideline"
*nl7*
Anders Lindgård
*sj* *nl19**lm 120*
78/1 *lm120**nl*
April 1978
*nl*
revised 1980-10-20
*rj**pn 5,0**ps 18*
*lm0*
Scope of the library*nl*
--------------------*nl2*
The scope of the library is to provide the users of the RC8000 computer with a manual
of all programs and algol8 procedures of common interest.
Most programs and procedures may be used on the RC4000 computer as well.
 The guidelines described
here has the purpose of making a uniform way of describing programs
and algol8 procedures
and having an easy way of updating and maintaining the whole system.. The descriptions
of programs, procedures and variables will be available in files on the RC8000
backing store. All descriptions are in english.
An example of a description of a procedure is  found in Appendix III, and
of a program in appendix VI.
*nl2*

The library is divided into  sub-libraries,
and a list of user relevant manuals is found in the
file "listman".
*nl*
*ps0*
*nl2*
Submitting procedures to the library*nl*
------------------------------------*nl2*
Users are invited to submit procedures of general interest to the
library. Slang coded procedures are normally not accepted to the
library. Exceptions are made if they are either very short or of
interest to a large number of users. There should be good reasons
for using assembly language. Speed is not considered a good reason unless it is
crucial.*nl2*
The submitted material should contain:*nl2**lm20*
*mt 1,    1.* a papertape in ISO (even parity) containing the procedure text 
(Algol preferred), a suitable algol8 test program and the necessary calls
of file processor programs to be able to compile the procedure and the
test program. See Appendix V.*nl2*
*mt 1,    2.* a paper tape in ISO (even parity) which contains the description of
the procedure in a form which can be used as an input for the program
Compose (The RC8000 textcomposing system) see Appendix IV.
 Descriptions should resemble the
descriptions in chapter 9 of the algol6 users manual (RCSL 31-D322)
as much as possible. It should contain the date of submitting and
authors name and affiliation as shown in Appendix III and IV.*nl2*
*mt 1,    3.* A form stating authors name, affiliation, degree of maintenance
 of the procedure etc. A blank form exist on the RC8000 backing
store named 'procform'. See Appendix I.*nl2*
*mt 1,    4.*A lineprinter copy of 1. and 2.*nl4**lm0*
*nl2*
*ps0*
Submitting programs to the library*nl*
----------------------------------*nl2*
Users are invited to submit programs of general interest to the
library. Slang coded programs are normally not accepted to the
library. Exceptions are made if they are either very short or of
interest to a large number of users. There should be good reasons
for using assembly language. Speed is not considered a good reason unless it is
crucial.*nl2*
The submitted material should contain:*nl2**lm20*
*mt 1,    1.* a papertape in ISO (even parity) containing the program text 
(Algol or pascal preferred), a suitable test data set and the necessary calls
of file processor programs to be able to compile the program and
run the program with the test data set. See Appendix VIII.*nl2*
*mt 1,    2.* a paper tape in ISO (even parity) which contains the description of
the program in a form which can be used as an input for the program
Compose (The RC8000 text composing system) see Appendix VIII.
 Descriptions should resemble the
descriptions in System 3 Utility Programs. Part two (RCSL 31-D494)
as much as possible. It should contain the date of submitting and
authors name and affiliation as shown in Appendix VI and VII.*nl2*
*mt 1,    3.* A form stating authors name, affiliation, degree of maintenance
 of the program etc. A blank form exist on the RC8000 backing
store named 'progform'. See Appendix II.*nl2*
*mt 1,    4.*A lineprinter copy of 1. and 2.*nl4**lm0*
*nl4*
*ps18*
Preparation of a procedure for submitting*nl*
-----------------------------------------*nl2*
The procedures should preferrable be programmed in Algol, unless
it is small fileprocessor manipulation procedure. Assembly
language coded procedures must be extensively commented
and must obey all the rules an algol  procedure should fulfil
see Code procedures in algol 5 (RCSL 31-D199).
 Algol programmed procedures must be
easily readable. Use long and descriptive names for parameters and
variables. Vary left margin according to 'begin'-'end' structure.
Avoid labels if possible.*nl2*
Do not try to make 'clever' programming. Straight forward procedures
are easier to read and maintain than trick coded.
Use english words only.*nl2*
References to  external algol8 procedures.
*nl*
In the procedure all procedures from Regnecentralen and all
system procedures from the computer department may be
called. Avoid use of other external procedures.
*nl4*
Preparation of a program for submitting*nl*
---------------------------------------*nl2*
The programs should preferrable be programmed in Algol or
pascal, unless
it is small fileprocessor utility programs. Assembly
language coded programs must be extensively commented
and must obey all the rules an fp utility  program should fulfil
see System 3 Utility Programs Part three programs (RCSL 31-D379). Algol programmed programs must be
easily readable. Use long and descriptive names for parameters and
variables. Vary left margin according to 'begin'-'end' structure.
Avoid labels if possible.*nl2*
Do not try to make 'clever' programming. Straight forward programs
are easier to read and maintain than trick coded.
Use english words only.*nl2*
References to  external algol8 procedures.
*nl*
In the program all procedures from Regnecentralen and all
system procedures from the computer department may be
called. Avoid use of other external procedures.
*np*
In pascal programs the algol external procedures are not
accessible.
*nl4*
*ps18*
Maintenance levels*nl*
------------------*nl2*
*lm 40*
*mt 1,level RC*
Software from Regnecentralen is fully maintained and updated 
by Regnecentralen. Error reports are available from the
operator.*nl1*
As we do not have a service contract with Regnecentralen and as
updated versions of the RC software is expensive theese errors
will most likely never be corrected.
*nl1*
*mt 1,level system* Systems software developed by the Computer Department
is fully maintained by the department. Errors together with
documentation should be reported to the departement.*nl*
*mt 1,level user*
Software developed
by the users may be maintained by the users. Errors should be reported
directly the user who developed the procedure with a copy to the
computer department.*nl1*
*mt 1,level other*
Software from other installations which is 
 maintained and updated by the other installa-
tion*nl1*
*mt 1,level none*Software which is not maintained at all.
*ef*

▶EOF◀