Mail Archives: djgpp/2001/06/30/09:33:40
> From: invalid AT erehwon DOT invalid (Graaagh the Mighty)
> Newsgroups: comp.os.msdos.djgpp
> Date: Sat, 30 Jun 2001 09:06:13 GMT
>
> On Fri, 29 Jun 2001 10:20:12 +0300, "Eli Zaretskii"
> <eliz AT is DOT elta DOT co DOT il> sat on a tribble, which squeaked:
>
> >This is usually a sign of a numeric bug in the code.
>
> No kidding, but in this case it went away when I switched to plain
> doubles universally.
Yes, I understand. And that precisely is the sign of a numerical bug,
in most cases I've seen.
> Hey, wait a damn minute, the info file said %f for doubles *and* long
> doubles.
No, it says doubles *or* long doubles.
> In any case, the core question remains unanswered: why was some code
> that didn't even use printf broken with long doubles but working with
> plain doubles? All it did was add, multiply, compare, and assign them
> with literals and variables. Not so much as a pointer or a conversion
> involved, and I don't think it even did any division...
Numerical computations are tricky.
- Raw text -