Pronounced "Tul-un-qweh-wag-nuf", call it Tulun for short.
It's one of those silly interpret-on-the-go programming languages that doesn't compile to bytecode. This means it's probably much less efficient than, like, any other programming language.
It's a functional programming language (i.e. functions are first class).
It doesn't make sense. Please ignore the fact that it doesn't make sense? Also, hide, far, far away from the source code. It might lash out and hurt somebody's brain.
# installationnpm install -g tlnccuwagnf# usage, seetulun help
Atom: Install the language-tulun package.
# python-style ##: multiline :#print("Hi!");
my_var => 42;print(my_var);
There are basically no control structures. In one command (each separated by semicolons) you can do the following:
variable_name => value,
variable_name -> new_value)
function(arg1, arg2, arg3))
But.. where are things like
if is a function. So you'll want to evaluate a call a function expression:
Here's an example of a program using all the things we showed above. Please excuse Liam's terrible ASCII labelling.
# Variable assign. ## v--- Variable identifier ## v vvvv--- A boolean literal. #x => true;# vv-- Get a variable using identifier "if", ## || this is built-in so all programs will ## || automatically have "if" as a variable. ## || v--- Get a variable using identifier "x", ## || | which we assigned earlier. ## || | v--- A function literal. #if(x,);
On the other hand, if you're just looking at it as a fun project we made as an experiment, go ahead and use it. I have nothing against you using it - I'd enjoy it if you used it! - but it's not a very good programming language, so don't expect something amazing.
No. Cool languages have specifications. But we're not sure making a specification for this simple(?) experimental project is either worth it or our style.