On Feb 10, 10:22 pm, "Michael J. Mahon" <mjma...@aol.com> wrote:
For any but tiny programs, starting with debugging would be
the "short end of the stick".
I like Applewin debugger :-P glutton for punishment?
Much better to start by doing
*serious* proofreading of the program to see if it all makes
sense.
yeah, thorough proofread definitely necessary.
And, as I noted before, using a tool to construct a list of
all the "words" in the program and their frequencies is a
very powerful tool for finding typos--more effective with
programs than a spell checker with English!\
what tool do you suggest? Any apple II word processors
with easily definable dictionary?