🚀 go-pugleaf

	I think I have a uncovered a bug in my version of Aztec C 3.60a.
I'm in  a function, have just set a variable I am going to return, but am 
entering a for loop that modifies some other variables.  At the end of the
for loop, my original variable (the one I first set and am going to return)
has been changed.  I put a printf in the loop and found that the change occurs
only on the last loop iteration.  I would include the code, but I thought I 
heard that there is a 3.60b version out.  I have not heard about this from
Manx, but if it is indeed out, maybe they already cured the bug.  If this
release is not out, I can post my code (it is short) and would like to know
if others have had similar problems and/or have reported it to Manx Techs.
If it is out, let me know, too, so I can contact Manx for the upgrade.

Thanks much

Scot   sjk@astro.as.utexas.edu
Aren't we all having fun?