<br clear="all">-- Pierre-Yves<br>
<br><br><div class="gmail_quote">On Tue, Oct 19, 2010 at 13:18, Max Horn <span dir="ltr"><<a href="mailto:max@quendi.de">max@quendi.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Looking at luaconf.h, it turns out that the Lua code indeed makes use of setjmp. That's rather bad news, as setjmp is not that portable. Instead of setjmp, Lua can apparently also use C++ exceptions -- something we have tried to avoid so far (and disabled in our build system). Still, I figure it might cause less harm to use those than to use setjmp. But either way, we'll have to deal with this.</blockquote>
<div> </div><div>You may want to ask for advice on the Lua mailing list: <a href="http://www.lua.org/lua-l.html">http://www.lua.org/lua-l.html</a> . This kind of question arises quite often.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
However, we then still would have the problem of pluto being tightly linked to the exact Lua version... However, note that from the pluto homepage <<a href="http://lua-users.org/wiki/PlutoLibrary" target="_blank">http://lua-users.org/wiki/PlutoLibrary</a>>, though, it sounds as if any Lua 5.1.x version would be acceptable. Is that correct?<br>
</blockquote><div><br></div><div>The .x versions are bug fixes. All 5.1.x versions should be source-code, bytecode and API compatible.</div><div>Here's the change log:</div><div><a href="http://www.lua.org/bugs.html">http://www.lua.org/bugs.html</a> </div>
</div>