Date: Fri, 24 May 2002 13:15:50 -0400 From: Mike Barcroft <mike@freebsd.org> To: Chris Hedley <cbh@teabag.demon.co.uk> Cc: freebsd-current@freebsd.org Subject: Re: strtod & sscanf on -CURRENT? Message-ID: <20020524131550.C26122@espresso.q9media.com> In-Reply-To: <20020524161853.U2404-100000@teabag.cbhnet>; from cbh@teabag.demon.co.uk on Fri, May 24, 2002 at 04:24:04PM %2B0100 References: <20020524133357.GA15486@sysadm.stc> <20020524161853.U2404-100000@teabag.cbhnet>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Hedley <cbh@teabag.demon.co.uk> writes: > On Fri, 24 May 2002, Igor Roboul wrote: > > Maybe I'm wrong, but I think that sscanf on -CURRENT does not work as > > expected. > > Interestingly I had some aggro with both scanf and strtod returning > somewhat random results recently (about 5th/6th May); I'm afraid I no > longer have the results or test programs but I ended up having to hack my > own routine together to get a reliable input. What I seem to recall is > that scanf didn't return the correct result at all, whereas strtod was > okay for the first couple of invocations within the same program, after > which it began to return garbage (I'm pretty confident that my program > didn't have a buffer overrun, it was a fairly short & simple effort) Would it be possible for you to reproduce the source to a small program that demonstrates the problem? Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020524131550.C26122>