Creep points can't be deactivated or removed

[ke]

Doing so in the creeppoint editor and clicking "Apply and quit" has no effect. Test case: deactivate or remove the default creep and skip points for grammar compilation – the behavior doesn't change, compilation isn't shown.

Are other point editors, adding points etc. also affected?

[jd]

Hmmm. Since the skip point is applied right away (before you have a chance to deactivate it), this is not exactly surprising behavior. Or do you mean if you compile the grammar a second time? The behavior in that case is still somewhat inconsistent anyway, at least when I am calling dcompile_gram a second time from console (the Parse menu items are still greyed out in my version).

[ke]

Sorry, my bad. It is possible to bring up the Kahina GUI by using the new dgo/0 predicate and thus to manipulate breakpoints before any steps arrive from the debugger. However, starting a compilation or parsing process also always starts a new Kahina session with the same GUI, but with a new tree behavior. And since default breakpoints are currently created with the tree behavior, any changes the user made to breakpoints are lost, so this is indeed expected behavior.

That at the moment every session starts with the default sets of breakpoints is not so desirable, of course, but issue #51 addresses this anyway.

[TarasBulba]

​Edgewall776 Software4906

[qbvqh]

​internet marketing