02-25-2014, 09:02 AM
(This post was last modified: 02-25-2014, 09:13 AM by paulclinger.)
(somehow the two responses have merged...)
Indeed. I updated the post to add space before the dot. Thanks for the heads up!
> The API definition docs examples seem a bit mis-formatted, my firefox is truncating the code without providing any scrollbar.
Yes, there are some long lines, but they should copy just fine. Still I'll update them to fit on the screen.
> Is there any documentation on adding a new "interpreter"? I'd like to try my luck with adding MCServer as the interpreter, but the existing interpreters are pretty dense with code, it's rather discouraging.
Take a look here: http://studio.zerobrane.com/doc-plugin.h...nterpreter . It's described as part of the plugin interface, but the interpreter code is exactly the same: in one case it's returned (from the interpreter) and in another it's used in AddInterpreter call.
Also, since you'd need to integrate auto-complete/API descriptions, you can do it from the plugin as well, which will leave you with one file instead of two. I'm working on a plugin repository that should provide an easy way to distribute and install those plugins.
Paul.
Yes, this can be problematic. What happens is this: you have an internal interpreter (statically linked), but socket library is linked against lua51.dll that is included with ZBS. So when you do require"socket" (directly or indirectly through require"mobdebug"), it loads socket.dll, which loads lua51.dll and you end up with two lua engines (and one of them may be "normal" lua and another LuaJIT), which leads to a crash.
There are two ways to deal with it:
(1) statically compile luasocket into your executable that has lua interpreter. That's what some engines do, like love2d.
(2) use a "proxy" DLL that replaces lua51.dll and will simply forward calls to your "static" executable. You can see some details here (http://studio.zerobrane.com/doc-lua52-debugging.html ) described in the context of Lua52 interpreter, but the same thing applies to statically compiled lua51 interpreter as well.
I can provide a proxy DLL if you want to experiment with it. In fact, I've been thinking about including it in the build/ folder of the IDE for cases like this. You'd just need to drop it into the same folder as your executable and the debugging should work.
(02-24-2014, 05:19 PM)xoft Wrote: Paul's links are 404ing on me, because the forum linkified the dot as well.
Indeed. I updated the post to add space before the dot. Thanks for the heads up!
> The API definition docs examples seem a bit mis-formatted, my firefox is truncating the code without providing any scrollbar.
Yes, there are some long lines, but they should copy just fine. Still I'll update them to fit on the screen.
> Is there any documentation on adding a new "interpreter"? I'd like to try my luck with adding MCServer as the interpreter, but the existing interpreters are pretty dense with code, it's rather discouraging.
Take a look here: http://studio.zerobrane.com/doc-plugin.h...nterpreter . It's described as part of the plugin interface, but the interpreter code is exactly the same: in one case it's returned (from the interpreter) and in another it's used in AddInterpreter call.
Also, since you'd need to integrate auto-complete/API descriptions, you can do it from the plugin as well, which will leave you with one file instead of two. I'm working on a plugin repository that should provide an easy way to distribute and install those plugins.
Paul.
(02-24-2014, 10:54 PM)FakeTruth Wrote: I tried to use remote debugging in my own project but it didn't work at all. I have compiled Lua into my project (static linked), could this be the problem and should I use the dll?
Yes, this can be problematic. What happens is this: you have an internal interpreter (statically linked), but socket library is linked against lua51.dll that is included with ZBS. So when you do require"socket" (directly or indirectly through require"mobdebug"), it loads socket.dll, which loads lua51.dll and you end up with two lua engines (and one of them may be "normal" lua and another LuaJIT), which leads to a crash.
There are two ways to deal with it:
(1) statically compile luasocket into your executable that has lua interpreter. That's what some engines do, like love2d.
(2) use a "proxy" DLL that replaces lua51.dll and will simply forward calls to your "static" executable. You can see some details here (http://studio.zerobrane.com/doc-lua52-debugging.html ) described in the context of Lua52 interpreter, but the same thing applies to statically compiled lua51 interpreter as well.
I can provide a proxy DLL if you want to experiment with it. In fact, I've been thinking about including it in the build/ folder of the IDE for cases like this. You'd just need to drop it into the same folder as your executable and the debugging should work.