Contact us Heritage collections Image license terms
HOME ACL Associates Technology Literature Applications Society Software revisited
Further reading □ Contents □ 1. Introduction □ 2. Basic symbols and comments □ 3. Identifiers, accumulators and cells □ 4. Types and values □ 5. Addresses and storage allocation □ 6. Simple cell designation □ 7. Assignment statements □ 8. Integer accumulator assignments □ 9. Real accumulator assignments □ 10. Long accumulator assignments □ 11. Cell assignments □ 12. Block structure □ 13. Procedures and labels □ 14. Conditional and control statements □ 15. Functions □ 16. Cell declarations □ 17. Synonym declarations □ 18. Storage allocation □ 19. Subcompilation and global storage □ 20. Define statements, conditional compilation and include statements □ 21. Compiler directives □ 22. FORTRAN/PLASYD mixed programming □ 23. ALGOL/PLASYD mixed programming □ 24. Useful library routines □ 25. Use of TASK macro to compile PLASYD programs □ 26. SMO cell designation □ 27. Compiler output □ 28. PLAN instructions not provided for in PLASYD □ Appendices □ 1: Errors and comments □ 2: 1900 character set □ 3: Syntax definitions in alphabetical order □ 4: Use of program XMED □ 5: 1900 order code □ 6: Code genereated for typical PLASYD statements □ 7: A sample PLASYD program □ 8: Less commonly used directives □ References
ACD C&A INF CCD CISD Archives Contact us Heritage archives Image license terms

Search

   
⟶ ACL ⟶ Literature ⟶ ICL 1906A manuals ⟶ PLASYD
⟶ ACL ⟶ Literature ⟶ ICL 1906A manuals ⟶ PLASYD
ACL ACD C&A INF CCD CISD Archives
Further reading ⇓

□ Contents □ 1. Introduction □ 2. Basic symbols and comments □ 3. Identifiers, accumulators and cells □ 4. Types and values □ 5. Addresses and storage allocation □ 6. Simple cell designation □ 7. Assignment statements □ 8. Integer accumulator assignments □ 9. Real accumulator assignments □ 10. Long accumulator assignments □ 11. Cell assignments □ 12. Block structure □ 13. Procedures and labels □ 14. Conditional and control statements □ 15. Functions □ 16. Cell declarations □ 17. Synonym declarations □ 18. Storage allocation □ 19. Subcompilation and global storage □ 20. Define statements, conditional compilation and include statements □ 21. Compiler directives □ 22. FORTRAN/PLASYD mixed programming □ 23. ALGOL/PLASYD mixed programming □ 24. Useful library routines □ 25. Use of TASK macro to compile PLASYD programs □ 26. SMO cell designation □ 27. Compiler output □ 28. PLAN instructions not provided for in PLASYD
Appendices
□ 1: Errors and comments □ 2: 1900 character set □ 3: Syntax definitions in alphabetical order □ 4: Use of program XMED □ 5: 1900 order code □ 6: Code genereated for typical PLASYD statements □ 7: A sample PLASYD program □ 8: Less commonly used directives □ References

APPENDIX 8: LESS COMMONLY USED DIRECTIVES

A8.1 ADDTO

This directive has a similar effect to SENDTO, the difference being that if the file used already contains subfiles, these will be erased by SENDTO, but left unaltered by ADDTO.

A8.2 DUMPON

This directive specifies the file to which the consolidator is to send the binary version of the program. It is necessary to have a DUMPON directive if an overlay program is being compiled, but otherwise the binary may be left in core to be run or SAVE'd.

A8.3 TRUSTED and PRIORITY

The trusted status of the object program may be set by means of the TRUSTED directive. Statuses Q, R, S, T are represented by the values 8, 4, 2, 1 respectively, and the parameter of the directive is formed by adding together the required values. The priority of the program may be specified as a two digit decimal number in the PRIORITY directive, but is meaningless under GEORGE.

A8.4 PROGEVEN and IGNORE

These directives, with parameters LOWER and/or UPPER, affect the placement of relativiser areas within the compiled program. The PROGEVEN directive causes the appropriate areas to begin on even number words of store. This can be used to increase the speed of running of heavily CPU-bound programs. The IGNORE directive prevents any SEGEVEN directives from taking effect.

A8.5 SEGMENTS

This directive causes the compiler to halt EC at the end of successful compilation. The default action is to delete FI #XPCK.

A8.6 OVERLAY and OVERCOMMON

The format of an OVERLAY directive is:

OVERLAY (area,unit) name 1,name 2,name 3...

The area number must be less than 255, and the unit number less than 1023. The names are the names of segments in the overlay. The OVERCOMMON directive is similar, but the names in this case are of global areas. There may be any number of OVERLAY and OVERCOMMON directives in a program description, but each may be at most one line in length.

A8.7 SEGMENT MODE

This directive is similar to PROGRAM MODE except that the address checking mode parameter is omitted, and the options MIXAM for mixed address mode and MIXBM for mixed branch mode are added. The default options are MIXAM and MIXBM.

A8.8 SEGEVEN

This directive is similar to PROGEVEN. If it is desired to remove the restriction that relativiser areas should begin on even numbered words of store, the directive SEGEVEN, without any bracketed qualifying sequence, may be used. If neither PROGEVEN nor SEGEVEN directives are used, relativiser areas are not restricted.

A8.9 SMOMACRO and COMPILESMO

If the SMOMACRO directive is used, all SMO instructions generated by the compiler will be converted into a sequence of instructions which will simulate the effect of the SMO. If the COMPILESMO directive is used, SMO instructions will be included in the object code where required. If neither directive is used, the compiler will check whether or not SMO instructions are available on the processor on which it is running, and act accordingly.

A8.10 READFROM

Use of this directive allows program source to be read from a direct access file in subfile format, where it has been placed by the utility program XMED, as described in Appendix 4. If a filename and subfilename are given, the compiler will attempt to open a direct access file of that name, and include the contents of the specified subfile as if they were part of the source code. If a filename only is given, all subfiles in the specified file will be included. If a subfilename only is given, it will be assumed to be in the file which is currently in use. The compiler uses DA14 for reading files specified by this directive.

⇑ 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