Xref: utzoo comp.lang.fortran:817 comp.lang.c:10944 Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!ll-xn!mit-eddie!husc6!uwvax!oddjob!ncar!noao!arizona!naucse!sbw From: sbw@naucse.UUCP (Steve Wampler) Newsgroups: comp.lang.fortran,comp.lang.c Subject: Re: Variable dimensioning in fortran (now in C) Message-ID: <756@naucse.UUCP> Date: 27 Jun 88 13:38:16 GMT References: <527@philmds.UUCP> Organization: Northern Arizona University, Flagstaff, AZ Lines: 22 From article <527@philmds.UUCP>, by leo@philmds.UUCP (Leo de Wit): > In article <749@naucse.UUCP> rrr@naucse.UUCP (Bob Rose ) writes: >>Close, but ... I assume you are using calloc to zero the array, but >>the whole world is not a VAX. Try: >> >> [Bob's example using malloc() deleted] > > What makes you think calloc() is VAX-specific? I checked with K&R: . I'm pretty sure Bob was not worried about calloc() existing, just that it may do the wrong thing. The bit pattern for 0.0 is not all 0 bits on all machines. What's needed is an falloc() (filled alloc()), where the value to fill (and the size, I suppose) are passed as arguments. . . . . .(sigh, inews fodder) -- Steve Wampler {....!arizona!naucse!sbw}