fut

From https://github.com/fusionlanguage/fut/discussions/119#discus... > I've read about Haxe in 2000s, before I started my work on Fusion. They have different design goals: in Haxe you create whole apps, in Fusion you create components to be used from other languages. Haxe has syntax similar to the (now dead) ActionScript, Fusion is similar to C#. Fusion transpiles to C, D, Swift, TypeScript, OpenCL and Haxe does not.

I've just learned that Ć is no longer a viable name (thankfully). Now it's Fusion Programming Language (or fut?) https://github.com/fusionlanguage/fut

I had a look at the repo in https://sourceforge.net/p/recoil/code/ci/master/tree/ - I think the meat of it is a giant file called 'recoil.fu' (22481 lines long) [edit] it is written in the 'Fusion Language' https://github.com/fusionlanguage/fut (and not https://gaelduval.com/introducing-fusion-the-ultimate-progra... !) - there's a playground at http://fusion-lang.org/ . I'd never heard of it before but seems a bit like Haxe perhaps?

Interesting find: one of the implementations is written in “Ć”, which transpiles cleanly into multiple languages: https://github.com/pfusik/cito Haxe comes to mind but this seems a lot simpler.

Let's discuss it in https://github.com/pfusik/cito/issues/30

Still I find the https://github.com/pfusik/cito simpler to explain what it exactly does with the short example. @pfusik please maybe put that example also in `ci.md`.

> Are there any samples of the final sources? https://github.com/pfusik/cito/issues/21 I generally check-in just the Ć source and not the translations, but if you want a quick look at the generated C code, here's some: https://sourceforge.net/p/asap/code/ci/master/tree/asap.c > if there's a error/bug in the generated code am I actually going to debug and parse it effectively? Generated code may be "readable" but it is it understandable? I had no problems with that so far. Nim adds a lot of boilerplate code in C output. cito sometimes adds a few lines here and there, but mostly it looks like the code you would write directly.

They do leak memory sometimes. Cito frees variables, but not temporary values. It also has no chance of knowing whether a third-party function takes ownership of an object or not. The simplest example is string interpolation, I've just submitted an issue: https://github.com/pfusik/cito/issues/26

Changed above from https://github.com/pfusik/cito. Thanks!

Looks like the parser is hand crafted using recursive descent method: https://github.com/pfusik/cito/blob/master/CiParser.cs I did not look closely but writing parser without any tooling is asking for troubles, from parsers that enter infinite loops to not handling parse errors properly. ANTLR is way better for writing parsers for simple languages.

Better intro: https://github.com/pfusik/cito/blob/master/ci.md