Re: Scite-debug: function call on multiple lines

["steve donovan" <steve.j.donovan@...>]

I've hit this before, it seems to be a RemDebug issue (in other words,
I don't understand it ;))

I'm going to do an official LuaForge release soon, so any feature
requests are welcome. For one thing, it will be possible to set the
Lua executable name as a SciTE property. I am also putting 'watches'
into RemDebug.

RemDebug is perhaps overkill for most Lua debugging, unless you really
need to debug a remote process. I shall look at that variant of
RemDebug which isn't remote ;)

Another idea I'm chasing is a limited form of edit-and-continue.
Limited, because you won't be able to change _local_ variables and
functions. But maybe I should just release ;)

steve d.

On Nov 23, 2007 12:11 AM, Shmuel Zeigerman <shmuz@actcom.co.il> wrote:
> > local b = ""
> > b = string.sub(
> >   "abc", 2)
> > print(b)
>
> The above code has a breakpoint on its line 2.
> When it stops on the breakpoint and is continued via either
> "step" or "step over", the following error is produced:
>
> > lua: mytest2.lua:2: attempt to call field 'sub' (a table value)
> > stack traceback:
> >       mytest2.lua:2: in main chunk
> >       [C]: ?
>
> However, if the function call isn't split on two lines,
> then the script runs just fine:
>
> > local b = ""
> > b = string.sub("abc", 2)
> > print(b)
>
> Comments?
> --
> Shmuel
>