LuaVerge
Displaying 1-1 of 1 total.
1
Please enter a numerical value for the importance of this sticky.
Enter 0 to unsticky.
Kildorf

If there's anyone out there using the Lua bindings for Verge, here's a note about an issue that has had me tearing my hair out for the last 24 hours or so. Overkill helped me figure out what was going on here.

By default, all of the Verge stuff (its variables and its functions and whatnot) all got tossed into a table called LuaVergeRaw. This was kind of a pain to work with so one of the things that you could do was to import all of that table into the global namespace, _G. Unfortunately this had the side effect of clobbering the first-tier variables like xwin and timer. (Well, specifically, you could get their value like you were supposed up to the moment you tried to assign anything to them; after that your value of the variable and the engines became unsynced.)

In any case, Overkill and I, being the primary users of Lua in V3, had a quick chat and decided the best solution here was to just use the LuaVergeRaw table, but give it a better name. We renamed it to v3, because it's short and in keeping with Lua's style for libraries.

In any case, if you have done any LuaVerge development, be warned that the newest version in the SVN (checked in about five minutes ago) will probably break your code. Sorry about that.

(By the way, for those who follow such things: My host is currently down so this is going to have to server for my weekly Gruedorf post until it's fixed.)

Posted on 2008-02-03 17:49:13 (last edited on 2008-02-03 19:20:04)


Displaying 1-1 of 1 total.
1
 
Newest messages

Ben McGraw's lovingly crafted this website from scratch for years.
It's a lot prettier this go around because of Jon Wofford.
Verge-rpg.com is a member of the lunarnet irc network, and would like to take this opportunity to remind you that regardless how babies taste, it is wrong to eat them.