Cyclone was supposed to be a safer dialect of C. Shouldn’t it have replaced C by now, while also adding some improvements and reducing the burden of legacy code?
Oh you’re right. The website wasn’t giving those vibes that’s for sure, and the wiki didnt suggest what license it was distributed under during its lifecycle. Was it always open source do you know?
The project is almost 24 years old, the same age as me. It does not appear to have any sort of license in it’s earlier stage, but later on, they’ve added GPL 2.0 and LGPL 2.1.
Cyclone is no longer supported; the core research project has finished and the developers have moved on to other things. (Several of Cyclone’s ideas have made their way into Rust.) Cyclone’s code can be made to work with some effort, but it will not build out of the box on modern (64 bit) platforms).
I read their webpage, but it is really vague. From a legacy point-of-view, wouldn’t it be better to incrementally add better language features, and if there happens to be a huge, breaking paradigm shift, initiate necessary refactoring of code base?
Add comment