Re: No Subroutines (was Re: Debugging many subprocedures)

Joe Pluta wrote:
> 
> And procedures can be misused most horribly.  One of the worst offenses
> I see is procedure with a bunch of return opcodes strewn throughout it.
> At least with a subroutine you can stick a breakpoint on the ENDSR and
> know it will get there.
> 

Joe, you can set a breakpoint on the P-B and P-E specs of a subprocedure
- no matter where the RETURN statement was, you'll always hit the P-E
statement.  (I made the P-E breakable mainly because of procedures that
end with a loop with conditional statements inside the loop.  It can be
difficult to get control just before the procedure ends.)