Flex machine

For other uses, see Flex (disambiguation).

Not to be confused with FLEX (operating system) or FlexOS.

The Flex Computer System was developed by Michael Foster and Ian Currie of Royal Signals and Radar Establishment (RSRE)[1] in Malvern, England, during the late 1970s and 1980s. It used a tagged storage scheme to implement a capability architecture, and was designed for the safe and efficient implementation of strongly typed procedures.

The hardware was custom and microprogrammable, with an operating system, (modular) compiler, editor, garbage collector and filing system all written in ALGOL 68RS.

There were (at least) two incarnations of Flex, implemented using hardware with writable microcode. The first was supplied by Logica to an RSRE design,[2] and the second used an ICL PERQ.[3][4] The microcode alone was responsible for storage allocation, deallocation and garbage collection. This immediately precluded a whole class of errors arising from the misuse (deliberate or accidental) of pointers.

A notable feature of Flex was the tagged, write-once filestore. This allowed arbitrary code and data structures to be written and retrieved transparently, without recourse to external encodings. Data could thus be passed safely from program to program.

In a similar way, remote capabilities allowed data and procedures on other machines to be accessed over a network connection, again without the application program being involved in external encodings of data, parameters or result values.

The whole scheme allowed abstract data types to be safely implemented, as data items and the procedures permitted to access them could be bound together, and the resulting capability passed freely around. The capability would grant access to the procedures, but could not be used in any way to obtain access to the data.

Another notable feature of Flex was the notion of shaky pointers, more recently often called weak references, which points to blocks of memory that could be freed at the next garbage collection. This is used for example for cached disc blocks or a list of spare procedure work-spaces.[5]

COMFLEX, a packet switching network capable of transmitting data at magnetic-disc speed, was developed alongside Flex. It made feasible the use of remote file-stores, remote capabilities, and remote procedure calls.[6]

## See also

[edit]

* Royal Radar Establishment Automatic Computer
* Ten15
* PS-algol

## References

[edit]

1. ^ Terry, Phil F.; Wiseman, Simon R. (June 1988). On The Design And Implementation Of A Secure Computer System (PDF) (Report). Royal Signals and Radar Establishment. RSRE Memorandum No. 4188. Archived (PDF) from the original on 3 May 2014.
2. ^ Foster J M, Moir C I, Currie I F, McDermid J A, Edwards P W (October 1979). An Introduction to the FLEX Computer System (Report). Royal Signals and Radar Establishment. Report No 79016. Archived from the original on 20 July 2018. Retrieved 12 February 2018.`{{cite report}}`: CS1 maint: multiple names: authors list (link)
3. ^ Foster J M, Currie I F, Edwards P W (July 1982). Flex: A Working Computer with an Architecture Based on Procedure Values (Report). Royal Signals and Radar Establishment. RSRE Memorandum No. 3500. Retrieved 12 February 2018.`{{cite report}}`: CS1 maint: multiple names: authors list (link)[dead link]
4. ^ Tombs, D. J.; Bruce, D. I. (November 1991). The Evolution of Ten15 (PDF) (Report). Royal Signals and Radar Establishment. Archived (PDF) from the original on 24 September 2015.
5. ^ Currie I F, Foster J M, Edwards P W (December 1985). PerqFlex Firmware (Report). Royal Signals and Radar Establishment. Report No 85015. Retrieved 6 February 2018.`{{cite report}}`: CS1 maint: multiple names: authors list (link)[dead link]
6. ^ McDermid, J.A. (November 1980). "Design and use of Comflex - a hardware-controlled packet switch". IEE Proceedings E - Computers and Digital Techniques. 127 (6): 233. doi:10.1049/ip-e.1980.0048. Archived from the original on 13 February 2018. Retrieved 12 February 2018.

## Further reading

[edit]

* Martin C. Atkins:  An Introduction to Ten15 - A personal retrospective.[permanent dead link] (includes a section about RSRE's Flex)

* v
* t
* e

Object-capability security

Concepts|

* Principle of least privilege (PoLP)
* Confused deputy problem
* Ambient authority
* File descriptor
* C-list
* Object-capability model
* Capability-based security
* Capability-based addressing
* Zooko's triangle
* Petnames

Operating systems,
kernels|

* Capsicum
* Fuchsia
* Genode
* GNOSIS → KeyKOS → EROS → CapROS
* Hydra
* iMAX 432
* Midori
* NLTSS
* seL4
* HarmonyOS (HarmonyOS NEXT)
* Phantom OS

Programming languages|

* Caja–Cajita
* E
* Joe-E
* Joule

File systems|

* Tahoe-LAFS

Specialised hardware|

* BiiN
* Cambridge CAP
* Flex
* IBM System/38
* Intel iAPX 432
* Plessey System 250
* CHERI

*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template