Then click "Enable Breakpoints", and toggle a breakpoint on the line "if(dVal<0) xVal = -exp(ln(-dVal)/3);", then on the Code Builder's LabTalk Console I type "mycube", and then type "dcuberoot(-8)".
The result: Nothing happened! It did not pause the program at the breakpoint, nor did the console return "-2" as final calculation result. It was just nothing returned.
Question:
How can I pause the problem in debug mode at the breakpoint?
LabTalk function is new and when more people are using it, we will put in the effort to hook up break point support. Currenly, you can use break point with ogs file section scripts.
Before that, you have to use the good old technique of dumping values in your function. And you can also use the type command to dump more info. You can also use the #! technique to keep the debugging code and wake them up only via @B=1, see
LabTalk function is new and when more people are using it, we will put in the effort to hook up break point support. Currenly, you can use break point with ogs file section scripts.
Before that, you have to use the good old technique of dumping values in your function. And you can also use the type command to dump more info. You can also use the #! technique to keep the debugging code and wake them up only via @B=1, see
Having the #! marking will make it easy for you to remove them once you know the function is working well.
CP
Yes, I have tried your technique, at the same time I was imagining that without resorting breakpoints how an experienced programmer might be smart enough to use such technique with efficiency, and even treat it as a shortcut. Maybe yes, they can do it. However, as a greenhorn, Breakpoints support is wanted!