🚀 go-pugleaf

In article <HIacndmZkvBvgy6gXTWcoA@comcast.com>,
CM <mckenzie992@comcast.net> wrote:
>
> [...]  I believe I have corrected all the errors however a
>huge mess at run-time.  again, not sure what direction to take, if you could
>be so kind as to give your feedback (or anyone else for that matter)

Here's a piece of advice for your *next* program (probably too late to do 
any good on this one):  *don't* try to write and debug the whole thing at 
once!  As you've seen, this leads to tons of compiler errors, and then if 
you have logic problems it can be a major task to straighten them out.

Instead, you should first sketch an outline of the overall structure of 
the program, then write and debug it in stages, a few lines at a time.  As 
you get more experience, you'll be able to make each stage bigger.  Add 
extra output statements to verify that variables contain what they're 
supposed to contain, loops are working the way they're supposed to work, 
etc.  When you're done testing and debugging, remove those extra output 
statements.

Oh, and get in the habit of indenting and formatting your code 
consistently as you write it.  It will make it a lot easier for you to see 
problems.

-- 
Jon Bell <jtbellap8@presby.edu>                     Presbyterian College
Dept. of Physics and Computer Science        Clinton, South Carolina USA