🚀 go-pugleaf

In <3v8ahp$3u0@ftcnews.nrcs.usda.gov> ute@feinde2.ftc.nrcs.usda.gov (Ute R. Willmore) writes:
>Richard A. O'Keefe (ok@goanna.cs.rmit.edu.au) wrote:
>: ute@feinde2.ftc.nrcs.usda.gov (Ute R. Willmore) writes:
>: >A rough pseudo code example:

>: >if (next value should be float)
>: >  array[i].val_ptr = calloc a double
>:                       ^^^^^^

>: This is not on your topic, but why on earth are you using calloc()?
>: Calloc() buys you precisely two things that malloc() doesn't:
>:  -- it takes longer
>:  -- it traps you into writing non-portable code.

>It also buys me initialized memory, and I need to ensure I don't have garbage
>in the array, since that will cause problems when I display the data later.

No, it doesn't. The effect of setting all bytes of a floating point type to 0
is undefined; it certainly doesn't in general set the floating point value
to 0.0. (That's what the second point above is talking about.)

-- 
Alan Stokes (alan@rcp.co.uk)
RCP Consultants Ltd
Didcot, UK