Lily 0.18

>>56998703
Is your IQ sub-20 or does it sometimes reach the low 40s?

Good job making another new language that nobody will ever use.

>>56998783
Not having users doesn't bother me. The project is large enough that it keeps me occupied.

>>56998804
Well if it's what you like to do then good for you.

You couldn't have made a more generic-looking language if you'd tried.

Does this language solve any particular class of problems well? Or is it thoroughly "general purpose"?

>>56998904
Suppose you need an embedded language, but you need one that's statically typed. You can embed Lily the same way you embed Lua, because the interpreter doesn't write global data. Only, Lily is statically-typed.

Or maybe you're doing embedded work and you're in a low memory situation or you want to limit gc pauses. Lily's type system allows it to rely on reference counting to avoid gc pauses, which can be unpredictable.

Or maybe you're using PHP because it has templating (that whole code between tags bit). The interpreter has templating built into it, so it's possible to transition over to a language that's statically-typed but keep that same abstraction.

>>56998993
>Or maybe you're using PHP because it has templating (that whole code between tags bit). The interpreter has templating built into it, so it's possible to transition over to a language that's statically-typed but keep that same abstraction.


did you mean transition to dynamically typed or really transition from lily to static typed there?

>>56999109
Lily is statically-typed throughout. But it also has PHP's 'code between tags' idea, if you start the interpreter in tagged mode. The default, though, is in standalone, where everything is code. When it's loading an import, the import is always loaded in code-only mode, so there's a distinction between what's the front (the templating pages), and what's not (strictly code parts).