Debugging (breakpoints etc.)

[Mariusz Grecki]

Hi,

I have started to think about gedit plugin for debugging nsp scripts and I found substantial problem... Although I can execute the nsp script line by line under the supervision of gedit I have no idea whether the breakpoints are available in nsp. In scicoslab they exist and they are used by scipad. How it looks like in nsp? I did not find and "setbpt" string except in file reader.txt. Without breakpoints implemented in nsp an efficient debugging seems not possible for me.

Another problem (which also exist in scicoslab) is lack of information about next line to be executed. To decide which line to execute next I would have to parse the source, that has no sense since nsp parser is doing that already. In scipad this problem was solved by dirty workaround (setting breakpoints everywhere). Certainly it can be applied in nsp as well but much more elegant solution would be to have access to the information about next line to execute. Could these 2 debugging functionalities be implemented in nsp? What are developer plans on that?

Greetings

Mariusz

[Jean-Philippe Chancelier]

Hello Mariusz,
Breakpoints in nsp are done like in scicoslab by inserting pause keywords in nsp code. The scicoslab primitives setbpt, delbpt are used to dynamically insert or remove pause keywords in function scripts. They are not implemented in nsp but could be.
Regards
jpc

--
You received this message because you are subscribed to the Google Groups "tumbi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tumbi+un...@googlegroups.com.
To post to this group, send email to tu...@googlegroups.com.
Visit this group at https://groups.google.com/group/tumbi.
To view this discussion on the web visit https://groups.google.com/d/msgid/tumbi/0749b0f8-7970-44f5-b739-df3f432bcae5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.