🚀 go-pugleaf

i reported this problem a while back (in net.micro, i think); it's effects
are even more widespread.  my UniSoft C compiler reuses one half of the
double result "register" as a scratchpad.  you'll see similar problems
with code like:
	double x[], atof();
	x[i] = atof(...);
the low-order fraction bits from the "atof" will get stomped by the
index calculation.  i "solved" my problem by avoiding "double"s
altogether.  i reported the problem to my micro vendor, who promised
to pass the word on to unisoft.  this was like last march... haven't
heard another word about it since.
	wayne ({decvax,ucbvax}!pur-ee!uiucdcs!uiucuxc!)hamilton