|
> From: Barbara Morris > > 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.) Oh my. As always, you ARE my hero, Barbara. It's the little things like that that will get you into Compiler Designer Heaven <g>. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.