Re: step over c function luaL_errorhttps://www.eclipse.org/forums/index.php/mv/msg/999275/1689449/#msg_1689449
Did you find a solution for this problem ?
I just try it, and it works for me :/ ...
Could you give me a sample of code based on the standard VM which allow me to reproduce it.
Simon
(sry for the late response)]]>Simon Bernard2015-03-23T15:49:28-00:00Re: Lua Attach Debug Issuehttps://www.eclipse.org/forums/index.php/mv/msg/1014258/1689443/#msg_1689443
Did you solve your issue ?
If not, could you give us a sample of code which allow us to fix this ?
Simon
(Sorry for the late response)]]>Simon Bernard2015-03-23T15:37:32-00:00LDT 1.3 M2https://www.eclipse.org/forums/index.php/mv/msg/1063793/1688480/#msg_1688480
This is a milestone version and there are still some bugs.
This release is focused on support of lua5.2 grammar (goto/label).
For an exhaustive list, read the new and noteworthy [1].
You can obviously try it [2] and give us your feed back.

Earlier I tried what I think is an earlier version of the debugger.lua. It was not following correctly after a break but it did get to the debug perspective etc. So I know that this stuff got pretty far along with the debugger.lua that was I think an earlier one,

Is there a step I missed?

Thank you for any assistance.]]>Rollin Crittendon2015-02-26T15:40:12-00:00step over c function luaL_errorhttps://www.eclipse.org/forums/index.php/mv/msg/999275/1621517/#msg_1621517
Everything works well except when the lua code calls a C function with pcall that rises an exception using luaL_error. It is like this:

a step over the pcall stops on a line after the call to function A, instead of stopping on the line just after the pcall.

Any idea of what am I doing wrong? Any solution?

Christian.]]>Christian Tenllado2015-02-17T23:42:37-00:00LDT 1.3 M1https://www.eclipse.org/forums/index.php/mv/msg/972274/1593300/#msg_1593300
This release is focused on support of lua5.2 grammar (goto/label).
For an exhaustive list, read the new and noteworthy [1].
You can obviously try it [2] and give us your feed back.

[1] https://wiki.eclipse.org/LDT/User_Area/New_Noteworthy/New_Noteworthy_1.3
[2] https://www.eclipse.org/ldt/#installation]]>Simon Bernard2015-01-30T14:46:30-00:00Re: Disable Error Markers or Add to Parser/Validationhttps://www.eclipse.org/forums/index.php/mv/msg/943852/1592998/#msg_1592998
There 're no easy way to change the parsing/validation markers for now ... It's seems the Lua community really like to change the grammar of Lua. (We don't see that in other language community). And it's really hard to propose good tooling if each user has its own grammar.
I suppose you have a lot of code based on your modified Lua VM, but you should consider to use standard grammar. This will give you access to a large current and future tooling for Lua.

To disable error markers in project explorer and problems views. Right click on the project/Properties/builders, then you uncheck ScriptBuilder. (if you still have markers in problem view you should delete them manually, they should not be recreated)
This solution is far from perfect, you will still get errors in editors and autocomplete will not really work. Sorry to be not able to propose better than this.]]>Simon Bernard2015-01-30T10:58:08-00:00Re: lua development tool without auto-completehttps://www.eclipse.org/forums/index.php/mv/msg/970545/1592963/#msg_1592963
Simon Bernard2015-01-30T10:30:33-00:00Re: lua development tool without auto-completehttps://www.eclipse.org/forums/index.php/mv/msg/970545/1591740/#msg_1591740
lai willy2015-01-29T18:16:03-00:00Re: lua development tool without auto-completehttps://www.eclipse.org/forums/index.php/mv/msg/970545/1591488/#msg_1591488
Simon Bernard2015-01-29T15:07:59-00:00