You would not determine that there is code you don't need with DEBUG --
the best option for that, in a sequential non-event driven program, would
be the cross reference utility which has a word UNCALLED. See the user
manual for details and instructions.

Its effectiveness on event-based programs, especially the windows based
application, has not been proven.

Rick

*********** REPLY SEPARATOR ***********

On 3/26/2002 at 6:23 PM Azedia of DOLFINA wrote:

>To be more clear; how would I used DEBUG to find out if there is code
>that I
>do not need? Can Iplce them around the ABOUT?
>
>
>
>> I took two samples files about.f and another winapp.f sample. This is
>what
>seemed to work but I am wondering if I have extra code that I do not need.
>How would I step through it with the debugger and isolate any code that is
>not being used?

----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
To unsubscribe, send subject "unsubscribe sftalk" to listar_at_forth.com
For help with listar commands, send subject "help" to listar_at_forth.com
Archives are located at http://www.forth.com/sftalk -- check them out!
Search the archives! Visit http://www.forth.com/search for details.
Received on Tue Mar 26 2002 - 20:58:21 PST