The internal do-op-loop runs until it sees a return value of zero from any op-codes. The RETURN statement within basic_opcodes.ops is really a keyword which gets parsed into an offset of the current PC counter based on the internally calculated size of the instruction (known at Configure time from opcode_table). Of course, this is based off my reverse engineering of existing code. I'm sure any of this is subject to change. As a note, another poster said that "end" is never executed which isn't currently true. -Michael Dave Storrs wrote: > Ok, that was pretty much what I thought. But then what is the 'end' > opcode for? It does a 'RETURN 0', which would increment the PC by 0 > opcodes...which either counts as an infinite loop or a no-op, and we've > already got a no-op op. >
- question about branching/returning Dave Storrs
- RE: question about branching/returning Gibbs Tanton - tgibbs
- RE: question about branching/returning Dave Storrs
- RE: question about branching/returning Gibbs Tanton - tgibbs
- Re: question about branching/returning Simon Cozens
- Re: question about branching/returning Dave Storrs
- Re: question about branching/returning Simon Cozens
- RE: question about branching/returning Gibbs Tanton - tgibbs
- Re: question about branching/returning Michael L Maraist
- Re: question about branching/returning Damien Neil
- RE: question about branching/returning Brent Dax
- Re: question about branching/returning Damien Neil
- Re: question about branching/returning Gregor N. Purdy
- Re: question about branching/returning Dan Sugalski
- RE: question about branching/returning Michael Maraist