scispace - formally typeset
Search or ask a question

Showing papers on "Software portability published in 1971"


Journal ArticleDOI
TL;DR: The method of transferring the BCPL compiler is described including the specification of OCODE which is the language used as an interface between the machine independent and machine dependent parts of the compiler.
Abstract: Methods of achieving program portability are discussed, with particular reference to the mobility of compilers. The method of transferring the BCPL compiler is then described including the specification of OCODE which is the language used as an interface between the machine independent and machine dependent parts of the compiler.

71 citations


Proceedings ArticleDOI
23 Mar 1971
TL;DR: The discussion will focus on the following features of the language and their implementation: portability, “debugability” of the source code, linked and/or packed dynamic structures which may extend onto secondary storage, and garbage collection.
Abstract: In programming a software package for group theoretic calculations one is faced with a number of problems including: 1 the size of the package, 2 the size of the problems to be run in terms of execution time and storage requirements, 3 the need for large dynamic data structures, 4 the desire to produce a portable package. Although the use of one of the existing languages may be a barely acceptable approach to one or two of these problems, none has been found to be a satisfactory approach to all four problems. Consequently only one serious attempt has been made to write such a package in a language other than the machine's native tongue. However, one can meet the minimal acceptable requirements for the language in which such a package can be written. In particular, the discussion will focus on the following features of the language and their implementation: 1. portability, 2. “debugability” of the source code, 3. linked and/or packed dynamic structures which may extend onto secondary storage, 4. garbage collection, 5. host system independent program overlay structure.

1 citations


Journal ArticleDOI
TL;DR: The requirements on an ALGol 60 system to enable it to act as a recipient of a software tool written in ALGOL are considered and the experience of implementing the translator–writing system, SID, on KDF9 is discussed.
Abstract: Software engineering research is facilitated by the availability of general purpose programs which aid the production of other programs. These may conveniently be termed ‘software tools’. Software tools in themselves often represent a significant amount of intellectual effort and so their portability between different computing environments is important. We consider the requirements on an ALGOL 60 system to enable it to act as a recipient of a software tool written in ALGOL. In particular, our experience of implementing the translator–writing system, SID, on KDF9 is discussed.

1 citations