cyclone VS cyclone

One of the inspirations for Rust, as I recall, was Cyclone: https://cyclone.thelanguage.org/

Which was/is a "safe" dialect of C; basically C extended with a bunch of the stuff that made it into Rust (algebraic datatypes, pattern matching, etc.) Though its model of safety is not the borrow checker model that Rust has.

Always felt to me like something like Cyclone would be the natural direction for OS development to head in, as it fits better with existing codebases and skillsets.

In any case, I'm happy to see this stuff happening in Rust.

It sounds like they re-invented Cyclone.

https://cyclone.thelanguage.org

Looks like it was a research project and is now abandoned: http://cyclone.thelanguage.org

The borrow checker is Rust's secret sauce. It's the one thing no other language has. (Except Cyclone I think, which is an unmaintained research language.)

Also, lifetimes are not the mechanism by which Rust ensures safety - it's a necessary side-effect of the approach that Rust has taken, and this has nothing to do with the issues that "plague" other languages. Region-based memory management techniques are neither new nor really innovative. https://cyclone.thelanguage.org/, which directly inspired Rust, had them, and the authors gave up working on it because the ergonomics were terrible, as is the case with Rust. Lifetimes are needed for the Rust compiler to reason about what it can reasonably allow at compile time, but it, along with the Borrow Checker (which provides the actual safety net) ensures that whole swathes of valid programs are disallowed because the Rust compiler is not smart enough (and probably never will be) to check that these programs are valid.

Just in case someone want's to try it I've did some work to allow build on linux (Ubuntu 18.04 and probably others too), you can see it here https://github.com/mingodad/cyclone .

I'm trying to have buildable versions of several compilers for learning and historical preservation and recently discovered "lwc" https://directory.fsf.org/wiki/Lightweight_C++ and apparently the latest version of it come with this pyvm version http://students.ceid.upatras.gr/~sxanth/pyvm-3.0/ -> http://students.ceid.upatras.gr/~sxanth/pyvm-3.0/pyvm-3.0.tar.bz2 but is not accessible anymore.

Does anyone have it and could share it ?

I already have a version 2.1 here https://github.com/mingodad/lwc and here https://github.com/mingodad/pyvm and here is some discussion with links https://github.com/mingodad/cfront-3/issues/6 .

I also have:

- Cfront3 https://github.com/mingodad/cfront-3

- Cyclone https://github.com/mingodad/cyclone

- Tinycc reeentrant https://github.com/mingodad/tinycc

Thank you in advance for any help !

Here https://github.com/mingodad/cyclone is my attempt to update the latest available cyclone code and fix it to build on more recents operating systems.

The first step is build as 32 bits as clean as possible then attempt to update to be able to also build for 64 bits.

Actually it's already working on Ubuntu 18.04 see the build here https://github.com/mingodad/cyclone/actions .

One of the main reasons to do it is to preserve for historical purposes .

There is also this other repositories that seems to try something similar:

https://github.com/moon-chilled/cyclonic