Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!uwm.edu!ogicse!news.u.washington.edu!serval!hlu From: hlu@eecs.wsu.edu (H.J. Lu) Newsgroups: comp.unix.bsd Subject: Re: strtod.c -- Where's the source Luke? Message-ID: <1992Sep18.222250.15477@serval.net.wsu.edu> Date: 18 Sep 92 22:22:50 GMT Article-I.D.: serval.1992Sep18.222250.15477 References: <8851@hq.hq.af.mil> <DJM.92Sep15104153@frob.eng.umd.edu> <1992Sep18.154311.20396@qualcomm.com> Sender: news@serval.net.wsu.edu (USENET News System) Organization: School of EECS, Washington State University Lines: 15 In article <1992Sep18.154311.20396@qualcomm.com>, karn@servo.qualcomm.com (Phil Karn) writes: |> In article <DJM.92Sep15104153@frob.eng.umd.edu> djm@eng.umd.edu (David J. MacKenzie) writes: |> >You can get strtod.c from the GNU shellutils 1.7, but when I tried |> >compiling it on 386BSD 0.1, gcc died from some internal error, with |> >signal 6 I think. I didn't try to figure out what it was about the |> >file that tickled the compiler bug; I just gave up. |> The only free strtod () which I know work are the one in libg++/iostream/dtoa.C in libg++.a 2.2 and the one hacked by me. Any other free ones are just toys. If your C compiler, as or stdio are linked with those strtod (), you are in trouble, just I like what I had with the early verions of the Linux C library. I learned a hard lesson. Trust me on this. H.J.