GOTO vs RETURN after a GOSUB

[rsocor01]

Better question is why you would use GOSUB without RETURN?

Yes, I'm asking myself the same question . Yes, your code looks better than mine. The program is probably overflowing the stack and halting like Dave said. Will the program restart from the beginning if the stack overflow is enabled?

[Dave]

Yes it should create an internal reset condition.

[pedja089]

Yes. It have almost same effect as MCLR pulled low, then high. Only 2 bits are different, if I remember correctly.

[rsocor01]

Thank you guys.

Robert

[Art]

If you want to be a cowboy for some reason you could have used GOTO instead of GOSUB.
Then you could GOTO back as well (instead of RETURN).

The difference between GOTO and GOSUB is that GOSUB loads the stack with the location it was called from so that a RETURN can go back there, but GOTO doesn’t need to do that.

BUT! using a GOTO to go somewhere, and another GOTO to go back, just means that neither GOTO had to exist, and you could have just dropped the routine right in where the GOTO was.

[Ioannis]

Also, using GOSUB reduces code size as this Sub can be called from various points of the program to do the same job, maybe with some parameters passing to it.

Keeps things structured.

Ioannis