IEinterrupt breaks executeIF

[jMarcS]

From forum user Dave: onGRtouch

He says v01.71 is not catching his onGRtouch, and that it worked okay in 1.70.

What's happening is that his onGRtouch: interrupt starts with an IF. The IfElseStack is not empty -- it has IEinterrupt on it. When executeIF() finds something on the stack, it checks:

if (q != IEexec) {

That needs to be

if ((q != IEexec) && (q != IEinterrupt)) {

otherwise the entire IF block is skipped. In Dave's case, that means it looks like the touch was ignored.

I can make that change easily enough (I have, and it makes Dave's code work again), but I don't know the IF/ELSE code well enough to know if that's all that's needed.

I think it's okay. With other IF/ELSE elements (ELSEIF, ELSE), the IF will already have put its own item on the IfElseStack. The IF is the only one that should have problems.

Paul, does that sound right to you?

[RFO-BASIC]

It looks to me like your change will do the trick.

I am going to start a new issue about making intermediate releases.

[RFO-BASIC]

It looks to me like your change will do the trick.

I am going to start a new issue about making intermediate releases.

[jMarcS]

GitHub is a little flaky -- apparently there was a network split last night or this morning. But I think I got it committed and pushed.