Originally Posted by Mahal
[Some programmer "mumbo jumbo" - non-programmers please feel free skip this:]NedK:
'typed' is a tricky word. Often it's used to mean 'statically styped' as opposed to 'dynamically typed', but both dynamically and statically typed languages can be 'strongly typed' and that's what's really important. Both the Kotori language and the K2 script language are strongly typed (=one will not get unexpected results by trying to run a script that uses data types in incorrect ways) and the Kotori language is also (partly) statically typed - every variable that's not of integer type has to be declared, and all variables not declared are assumed to be integers.
I don't plan on any 'select' with fall-through like in C/C++ since it's very error-phrone. Also, the 'select' of the K2 script language is non-fall-through. It's possible to use if and else if as replacements for 'select', but it may involve a small (probably very small) performance penalty. Maybe I'll use 'if' and 'else if' in the Kotori language and output 'select' statements in cases when it's possible. I'll see when I find time to finish it. For the time being the slight extension to allow for user-defined functions in K2 scripts integrated in the editor takes one pretty far.
Thanks, however I don't know if the velocity-based articulation switching script is really ready to use. For example, there are some "make_persistent"s missing, so settings might not be saved properly. If the script would be useful to you, I'll consider completing it. I wrote it mostly to explore what features might be useful in the Kotori language.
And I agree, a big thanks to Big Bob, Fizbin, and Theo!