The SETL programming language
setl.org
setl.org
After getting my Masters degree in the early 80s, I went to NYU for my Ph.D. with the intent purpose of working on SETL with Jack Schwartz. Unfortunately, by that time, Jack had moved on from SETL and onto the world of Robotics. Robert Dewar was too busy building Realia COBOL and was not taking on any additional Ph.D. students. So I floundered around NYU for a year before deciding to do my own commercial software, which was probably the best decision I ever made. Especially after seeing a lot of Ph.D. students at NYU who had been there for 10 years.
Just curious: what did you build, with your commercial venture/startup?
The original SETL was implemented in a language known as LITTLE, Dave Shields noted in an email: "SETL was implemented in LITTLE, a language based on FORTRAN that had fixed=length bitfields as a fundamental data type."
Early SETL was used by Robert Dewar's team to implement the first validated Ada implementation, known as NYU Ada/Ed. This implementation worked as an interpreter.
We have a printed copy of the original SETL based NYU Ada/Ed but we are still to find the original SETL implementation. Maybe somewhere in the Courant Institute or their alumni there is someone with an original magnetic tape from the DEC VAX machine that ran these implementations.
This got me interested. I may not have found what you're looking for, but I found something.
The current git repo's first commit is "based upon SSoS2I 1.0.1" [0].
[0] https://github.com/herrmanntom/setlX/commit/ae1e8a16fb1c15d8...
https://en.wikipedia.org/wiki/SETL
In my other reply in this thread I highlighted the lineage of SETL, I neglected to also mention that SETL was an influence on ABC that influenced Python.
I don't think anyone thinks GvR is incapable of removing the GIL. Given the comparatively tiny base of installed SETL software, surely it's a lot easier to check that any backwards-incompatible changes to SETL won't break any important installed software based on it than it is to do the same for Python?
(And, as a follow-up, I think it's fair to say that there is no such thing as a fully backwards compatible change. My background is with Perl more than Python, where the problem is especially acute; but I imagine with Python too, it is very hard to make a change where one can be totally sure that the behaviour being 'fixed' isn't behaviour that some piece of software somewhere out there relies on being broken in exactly the historically right way.)
Any older?
Anyone here ever tried it out?
The license is a bit of a mix [1], but sort of mainly BSD, but partly LGPL.
[0] https://github.com/herrmanntom/setlX
[1] https://github.com/herrmanntom/setlX/blob/master/license.txt
Some elements of setl eventually got their way into python ~15 years ago, namely: sets and list comprehension.
Archeology of programming...
The page also includes some SetlX programs.
Undated. From the Documentation page.
https://www.gnu.org/cgi-bin/estseek.cgi?phrase=setl&perpage=...