Jump to content

  • Log In with Google      Sign In   
  • Create Account


Member Since 19 Feb 2012
Offline Last Active Aug 12 2012 01:37 PM

Posts I've Made

In Topic: Robsut C++ bound scripting language

12 August 2012 - 06:51 AM


first of all, thanks for the reply. I will consider to have a look at it, even if it means to spend time studying lua's internals. I think this (http://lua-users.org...indingWithLunar) is a bit like what you said. Anyway, at a second thought, it seems your idea looks to be a very good solution: since it won't change often, it will remain stable and robust. Since I could add what I want, it will remain little, easy to maintain and fast.

To answer your second part: I want something that runs with C++ 03, which supports OpenGL 2.x... and that support lua 5.1 (or above). That's enough for me, and that should be enough for everyone.
If things work with luabind 0.9.0 but stop to work with luabind 0.9.1, or work with lua 5.1 but stop with lua 5.2, that simply means for me that there's something bad in these solutions, not with mine. Here (http://www.lua.org/versions.html), noone can read that something was broken between the last two releases, for example.
I know some will argue that GL 3.x and above deprecated many functions of GL 2.x and below, but this is something different. I expect minor verisons not to destroy intentionaly what was made in the just previous minor version.

For general concerns, linux distributions (at least in Debian) provide several versions of programs, ie c++ compiler with different minor versions, lua 5.1 and 5.2 ... which, normally, should help people to keep a coherent, stable and robust developping system. However this is not always easy, and when we do things alone (long time projects, in several years), it is important to consider dependency evolutions, ie, move to C++ 11, move to GL 3.X or even 4.X, use lua 5.2...
Another important point about linux distributions (at least for Debian), is that updates happen as long as the distribution is said in testing. At a point (like at this time), it began frozen, and program versions do not change that often, only to correct bugs and security issues.
To summerize this, I just want to say that it's important to follow the evolution, not to be stuck with a release, and minor versions (as I tried to say it above) are meant to correct bugs, to add minor functionalities, and to prepare to the next major release, not to destroy old functionalities.

Thanks again for your reply.