Greetings,
Over the past several months I've been privileged to experience RSRE Flex,
an operating environment for PERQ workstations (and a few other bespoke
machines before that). Flex is interesting for being a networked
capability-based system with a hypertext-ish user interface, and everything
is implemented in Algol 68. Closures (in the programming language sense;
called "procedures" in Flex) are a fundamental abstraction similar in
importance to how files are fundamental to Unix*.*
Flex was developed in the late '70s and the '80s by the Royal Signals and
Radar Establishment, a research lab of the UK Ministry of Defence. Its
influence on computing has been limited as far as I can tell: the same
researchers went on to develop the Ten15 abstract machine which begat the
TenDRA compiler, and that might be most of the story. Nevertheless, the
system remains fascinating (I think) if you get the chance to learn about
it. I've collected some Flex materials here: https://mg-1.uk/flex/flex.html
In a few weeks I'll be giving a talk and demonstration of Flex to a
technically well-informed but otherwise unfamiliar audience. I can
certainly fill the time with rich technical details and descriptions of
things like Algol 68 and the PERQ, but I'd like also to have more to say
about the circumstances that brought Flex about and the ways people
encountered it at the time. I'm also hoping to gather information that
might lead to a public release of Flex someday (another thing I've been
working on behind the scenes).
So this message is a general request for information and connections:
- Did you or did someone you know work in computing at RSRE in the '70s and
'80s?
- Flex was shared with people outside of RSRE in the '80s, mainly
universities and colleges from what I can tell. Did you encounter Flex
running on a PERQ in one of these settings?
- Did you ever use Flex under any circumstances? What for?
Also:
- Flex contains numerical routines in both Algol 68 and PERQ microcode that
bear copyright assertions by Numerical Algorithms Group Ltd (now nAG,
nag.com). Does anyone know someone at nAG who would be a sympathetic person
to approach about the disposition of this very old IP?
Many thanks, --T
As a matter of fact, I had already sent Scott an email, but did not get a reply.
> Date: Fri, 26 Jun 2026 08:57:24 -0400
> From: Ken Seefried <seefriek(a)gmail.com <mailto:seefriek@gmail.com>>
> Subject: [cctalk] Re: Looking for a paper in COMPCON '83
>
> You might reach out to the authors. I'm pretty sure S.B. Baden is Scott
> Baden @ UCSD.
>
> https://cseweb.ucsd.edu/~baden/
>
> KJ
I’m trying to get a copy of this paper:
S. B. Baden and D. R. Patel. “Berkeley FP — Experiences with a Functional Programming Language.
Conference Record of COMPCON ’83, San Francisco, California, pp. 274–277, March 1983.
and wonder if anyone on this list has a copy of the proceedings?
The source code is available in the tuhs.org archives and the manual is available in the supplementary documentation for BSD 4.2, but I am interested in what the author wrote about their experiences. (I’m working on a history of John Backus’s functional programming project; Berkeley FP is based on Backus’s work.)
Paul McJones
This is irregular, and I beg your indulgence, as it at least in light
of the recent Alpha EV6 discovery.
I have a story to tell you Mr. Stone, that you will be very glad,
amazed and fulfilled to hear and to know.
This is not the forum for such things, but I am a very little person
and could not hope to reach you in any other way.
Thank you gentlemen for your forbearance. I ask further of you even,
if you know Harold S. Stone, the author of High-Performance Computer
Architecture, please ask him to message me on facebook or call me. I'm
not hard to find, I'm @Technoid_Mutant on Youtube...
Again, my thanks.
Jeff
We've been working on restoring and powering up a fairly rare bird of IBM Midrange machine, the IBM System/38.
We had some good success this past weekend that I'd like to share.
https://crusty.computer/?p=89
June Work Recap: Edith – The Crusty Computer Club
crusty.computer
tl;dr: she powered up and no smoke came out and no sparks came out! There are several repairs needed but they are known and fixable.
Intel's x86 technology as in the 8086 came into existence for the
microcomputer-user at this time back in June 1978. It was a response to
Motorola's and Zilog's move to 16-bit processing. Still in use today...the
basic tech so to speak. Can it be unseated by RISC(Apple and such) and
Nvidia?
Happy computing.
Murray 🙂
Yes, DCALGOL is still around and actively used. It is a superset of the standard Extended ALGOL, and originally exposed some special APIs and data types for talking to the Datacom Processor front-end. Those APIs are still used, although the "front end" is now TCP/IP.
The language has since been extended with numerous other APIs for use primarily by system-programmer types. There is also a DMALGOL compiler primarily used internally with the DBMS, DMSII. All three ALGOL variants have been compiled from the same source code since sometime in the '70s.
DCALGOL would have been no different than ALGOL for dealing with tapes, and I'm surprised you found it harder to do with the MCP than with OS/360 EXCP I/O. Depending on the block and tape label formats, you may have had to do your own deblocking, and possibly read the tape as unlabeled, but the MCP I/O Logical I/O subsystem was quite rich even in 1975. You had to understand how the file attribute settings worked when dealing with non-native tape formats, however -- I've seen that trip a lot of people up. As an alternative, a variant of Logical I/O called Direct I/O was available, which is user-mode asynchronous I/O that reads and writes raw blocks. It's basically a thin wrapper around the MCP's internal Physical I/O mechanism.
I know this is water long over the dam, but I'd be interested in hearing what kinds of issues you encountered, and if possible, a reference to the DEC formats you were trying to read.
As a fan of BCPL (from the Alto), I only wish it was better documented.
For example, Tripos has next to no documentation on it including how to
compile and load it. Documentation on the runtimes is also lacking (and
that's where the rubber meets the road).
Unfortunately, the Alto changes were not picked up so it remains an
isolated branch (and *dead* by the definitions put forward).
I have found that a modernish Dell PC (win 7 era) when attached to a m4
9914 tape drive has issues when attempting to read 800dpi 9track tapes.
I/O errors that seem to be centered around variable block size microcode of
the modern scsi controller (?)
I've spent a number of hours on it and I could not even pull raw data off
an 800dpi tape. 1600 no problem. works fine.
is there a tweener box or scsi controller that will work in this situation?
what do other people do?
Bill