DW> set up some sort of "supervisor" which would watch a
DW> program as it is running for a long time, and take note of
DW> any bits that are never used.
If your code is properly formatted to the modular approach,
you should be able to find unused code simply by putting the
name of the SUB or FUNCTION in the Find utility and seeking
out all instances of its appearance in your code. If it is
never called, then you just delete it. You can have a code
module with all your favorite routines, and just load it as
a module, and then, when you are done, just check for calls
to the modules and delete the ones not being used from this
copy of your source. In this way, you can have a standard
toolkit module and not have to run back to the disk for a
special tool to include in your new program.
> ] And that's all I have to say about that. [ F. Gump ]........
---
---------------
* Origin: *YOPS ]I[* 8.4 GIG * RA/FD/FE * Milwaukee, WI (1:154/750)
|