Tuomo Valkonen <[EMAIL PROTECTED]> writes: > > Although I had no plans of writing the support anytime soon, I gave > Lua (I'm liking it even more than before!) and SWIG too a closer look, > after. SWIG documentation is immense and I have only glanced at it, > but it would seem to me that using SWIG, even if it had Lua support, > would severely limit what could be done and what could safely (mmmm... > userdata with watch-linked objects gc tags) be done. It would be nice > to be able to easily generate interfaces to many languages but I'm > currently inclined to not use SWIG.
I don't think we should have more than one extension language for Ion to avoid confusion, so there's no need to generate an interface for other languages. The problem is that writing Lua interfaces appears to be quite a long and tedious task. Not if you only write an interface for calling "Ion functions" and doing configuration, of course, but if we're going to wrap a lot of functions and objects it may require some kind of automation. Should we write our own tool instead or what do you suggest? /Pelle
