apple wrote:
On Feb 10, 11:36 am, "Michael J. Mahon" <mjma...@aol.com> wrote:And keep in mind that some of the errors will not be flagged by the compiler, but *will* change the meaning of the program.yeah, there's another step(s). get it to compile without errors. BRUN the program and see if it works right. If it doesn't, time to start a proofread or run it through Applewin debugger.
For any but tiny programs, starting with debugging would be the "short end of the stick". Much better to start by doing *serious* proofreading of the program to see if it all makes sense. 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!\ You will finds lots of "similar" "words" that should be the same, and any very low frequency words (like singletons) are suspect. This is a much easier way to find typos than debugging a program which "just happens" to compile. -michael NadaPong: Network game demo for Apple II computers! Home page: http://members.aol.com/MJMahon/ "The wastebasket is our most important design tool--and it's seriously underused."