stbenge wrote:
> Your input has been very helpful! I don't know why I didn't think to 
> print values to the console for debugging before, it's so useful :) Now 
> I will consider my data types and memory usage more carefully. Thanks 
> Darren!

No problem. Glad to help.

It's not the printing of values per se that helps. It's the "figure out what 
step isn't doing what you think it's doing."  Whether you use an interactive 
debugger, print statements, or hex core dumps, figuring out where the 
process first goes wrong is the most important step.  That's part of what 
makes unsafe languages (i.e., those that don't check array bounds for 
example) harder to debug - it's possible something goes wrong and breaks 
code completely unrelated to the broken code. With a safe language, the code 
does exactly what you wrote, regardless of what came before, even if what 
you wrote isn't what you wanted.

> P.S. I'm jealous. You live near some of the best mineral hunting grounds 
> in the U.S. ;)

I did not know that.


-- 
   Darren New, San Diego CA, USA (PST)
   There's no CD like OCD, there's no CD I knoooow!

Post a reply to this message