Okay, but the issues caused by the recent dev builds are pretty major. It's because std::string was replaced by a custom StringRef class so that strings would use pooled memory (meaning less allocations and stuff -- which is good, I agree).
But LuaVerge is broken as a result, cause the functions expect StringRefs to be passed instead of std::string, and it can't cast with LuaBind's templated crap.
Though the luabind devs did introduce a few new features in 0.8 that may fix it, it'd take a fair chunk of time to actually put that in: http://github.com/luabind/luabind/commit/e57f769493ef32e940d7e31471d1d81e5c605f68
In addition, me and zeromus were talking about making our own custom Lua wrapper and tossing out LuaBind, but that opens up many potentional bugs. Although, it'd mean we'd have full control over our binding...
Anyway, that's what's going on in recent dev builds.
So in other words, I'm thinking to save some headaches, people should use
http://www.bananattack.com/stuff/verge.exe at least until we fix it.