11–20 of 26 posts
> "The "small Lisps" are truly small, unlike, say, Lua." Well tinyscheme seems to be about half the size of Lua, which is not that different. Lua really is pretty small.
If you start exposing the engine in arbitrary fashion, things go south rather quickly; the scripting language will never stop finding more things it happens to need to get access to, and then you have an inner platform with boilerplate abstractions that make for worse tooling than whatever you started with.
Earlier quoted context omitted.
Guile LGPL makes it incompatible with commercial games on iOS (because exes are required to be statically linked). However, I think it's one of the best choices on other "more permissive" platforms.
The LGPL doesn't prohibit static linking. You are free to use static linking with the LGPL as long as you make the (potentially modified) LGPL source code and any other components of the linking process available. See section 4 d) 0) of the LGPL: http://www.gnu.org/licenses/lgpl.html In particular, iOS WebKit has been distributed in this fashion. You can download a source tarball from Apple that includes static binar…
| ... Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work ...
This is practically impossible to do with under Apple Store forcing digital signing of applications (forbidding combined work), even if the developer provides modified source code.
Earlier quoted context omitted.
The LGPL doesn't prohibit static linking. You are free to use static linking with the LGPL as long as you make the (potentially modified) LGPL source code and any other components of the linking process available. See section 4 d) 0) of the LGPL: http://www.gnu.org/licenses/lgpl.html In particular, iOS WebKit has been distributed in this fashion. You can download a source tarball from Apple that includes static binar…
Indeed, however, according to the following : | ... Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work ... This is practically impossible to do with under Apple Store forcing digital signing of applications (forbidding combined work), even if the developer…
The info on mission scripting is really good though!
My kneejerk reaction was "oh my god don't dump a general-purpose language into the runtime just to write mission scripts," but this is actually a good example of how to do it: The DSL defines some data structures that the C++ code uses, and has a direct handoff of the emitted results from Lisp into C++. Lisp doesn't have to interact with every frame of the game. If you start exposing the engine in arbitrary fashion,…
Embedded programming languages are really cool. Lua's still ruling the roost, as far as I've seen, but there are some nice options out there. I'm currently using mruby for a project and have been quite happy with it so far. The community around it is still somewhat thin, but the code quality is good and development is quite active. https://github.com/mruby/mruby
Out of interesting Lisp dialects, there's also PicoLisp (http://picolisp.com/wiki/?home) which looks like it should be well suited for embedding, but I didn't find any docs for how to do this with a quick search.
> "The "small Lisps" are truly small, unlike, say, Lua." Well tinyscheme seems to be about half the size of Lua, which is not that different. Lua really is pretty small.
Indeed. TinyScheme being a single file of C code hides this fact at a first glance. I didn't want to diminish Lua, which I find quite good too (I wish LuaJIT was usable on iOS), but I was really looking forward to dive into Lisp.
Android L is also going to kill jit compilers as well alas, see [1]
Earlier quoted context omitted.
Indeed. TinyScheme being a single file of C code hides this fact at a first glance. I didn't want to diminish Lua, which I find quite good too (I wish LuaJIT was usable on iOS), but I was really looking forward to dive into Lisp.
LuaJIT is usable as an interpreter on iOS, just not a jit compiler. It is a very fast interpreter, but obviously this is not ideal (and the ffi is slower without jit). Android L is also going to kill jit compilers as well alas, see [1] [1] http://lwn.net/SubscriberLink/609511/53f3d97eed238d55/