xl

From what I can read the author got really unlucky with some kind of radical API changes. Maybe at that time the LLVM team was a bit less serious with deprecations ? I use LLVM since v9, nowadays I'm stuck on v15 (that's not because of LLVM btw). Between the two versions there's been a radical change too, i.e "opaque pointers", but the transition was rather smooth as we were provided, for a long time, the two versions of the functions affected by the change. Maybe the LLVM team got more serious since the author experienced the said difficulties ? Other thing I note is that the author uses the CPP API. I use the C one which exposes only a high-level subset of the CPP one. This encourages a saner use of LLVM, a more concrete separation between the front-end and the mid-end, although sometimes there are limitations. A simple example of what

The really ugly stuff is here: https://github.com/c3d/xl/blob/master/src/llvm-crap.cpp

I realized I forgot to share my most memorable piece of code ever: llvm-crap (Compatibility Restoration Adaptive Protocol) https://github.com/c3d/xl/blob/master/src/llvm-crap.h

You can do exactly that, and this is how this is defined in the built-in library https://github.com/c3d/xl/blob/fast/src/builtins.xl#L222 How it works is what I tried to document in the document above. The trick is to have some fixed semantics on how rewrites are done, but a lot of freedom in how this is implemented. And this is far from perfect ATM. For example, if you write "X is 2", this can be implemented as a constant, as a function returning a constant, or as a macro. However, if you write "X is seconds" in Tao3D, where "seconds" returns the current number of seconds in the clock, then it can no longer be a constant value. You still can use macro replacement (or inlining) or turn it into a function. More details here: https://xlr.sourceforge.io/#compiling-xl

See the code around here to answer that question: Definition of 'if' statement: https://github.com/c3d/xl/blob/fast/src/builtins.xl#L155 // If-then-else statement if [[true]] then True else False is True if [[false]] then True else False is False if [[true]] then True is True if [[false]] then True is false Definition of loops (https://github.com/c3d/xl/blob/fast/src/builtins.xl#L222) // Loops while Condition loop Body is if Condition then Body while Condition loop Body until Condition loop Body is { while not Condition loop Body } loop Body is { Body; loop Body } for Var in Low..High loop Body is Var := Low while Var < High loop Body Var := Var + 1

And when you're done either smiling or shaking your head, Useful: - https://github.com/marketplace/actions/create-my-awesome (needs maybe htmx and typsense?) - https://github.com/python-eel/Eel Cool: - https://github.com/c3d/xl - maybe smalltalk xstreams Can't decide: - https://github.com/Wanderson-Magalhaes/Modern_GUI_PyDracula_... I''m going to bed.

Thank you! I was actually looking for something specific about parse trees vs S-expressions. That would be https://github.com/c3d/xl/blob/master/doc/HANDBOOK_1-syntax.... But I'm reading the whole thing now. Very interesting language! I don't see myself using it in production any time soon, but it looks like a wonderful tool for programming languages research. Thank you again!

Well, a starting point would be this: https://github.com/c3d/xl/tree/master/doc. It's not finished, but it gives you a good idea. For Tao3D, you have https://tao3d.sf.net.

Disclaimer: Author of the language / web page speaking. This one is hopelessly outdated. See https://github.com/c3d/xl for the current state of things. A bit of history of the language here: https://github.com/c3d/xl/blob/master/doc/HISTORY.md. Warning: this is currently under heavy repair / refactoring, so Nothing Works™. An interesting (if old, 2010) application of the language here: http://tao3d.sourceforge.net. Contributions and ideas welcome.