Hello Paul Sorry for the slow response to you message. That's good news, I hope you can manage to figure out how to make all 3 run times co-exist, it would make life simpler for your users. While I am writing can I ask another newbie level question please ? I don't really understand how ZBS does it magic and manages to debug scripts set breakpoints etc. When you are running Lua 5.1 interpreter and a simple script on a PC, I don't believe that ZBS is using Luasocket to do the interfacing in this scenario ? Please correct me if I am wrong ? If I have a simple program that I have written that essentially is just a PC exe that contains a statically linked Lua 5.1 source code with a bit of additional C code functionality for my specific App. (For example I am simulating some Relay outputs and switch inputs) When the PC exe runs, it opens a Lua script to control the relays, look at the switch inputs etc From previous messages I think you said it isn't possible to use ZBS to debug that script in this scenario ? I don't really understand why this isn't possible as my EXE isn't that different to just a standard compilation of Lua 5.1 source. Could you explain what the difference is and why this wouldn't work, it would be interesting to understand this better. Thanks Paul Geoff > Date: Thu, 14 Nov 2013 22:26:06 -0800 > Subject: [ZeroBrane Studio] Re: couple of questions > From: paul@xxxxxxxxxxxxx > To: zerobrane@xxxxxxxxxxxxx > > >> You know how easily things get confused, we will have folks putting gotos > >> in the script that work fine on the PC but then don't work on the target. > >> I just feel more comfortable keeping things in sync version wise. > > > That's an interesting point. It may be possible to "fix" with compile > > time checks, but if you really want to use Lua 5.1 interpreter, I may > > consider including it back. I don't see a way to make the DLLs > > co-exist on Windows, so it would mean including yet another copy of > > luasocket that is built against a Lua 5.1 dll. > > Just a quick update for Geoff and others interested in this topic. I > might have found a way to make all three run-times (LuaJIT, Lua 5.1 > and Lua 5.2) to co-exist on Windows and OSX and to work well with > different packaging mechanisms (LfW and LuaDist). I'm still working on > the details and plan to have something to test early next week. > > Paul. >