[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: [BUG]0/1=?
- From: Rob Kendrick <lua-l@...>
- Date: Thu, 22 Jan 2009 18:31:30 +0000
On Fri, 23 Jan 2009 02:25:46 +0800
KHMan <keinhong@gmail.com> wrote:
> > I'm trying to work out what causes this, and if it's intentional,
> > why it is desirable. So far, I've failed.
>
> The specification for strtod in IEEE Std 1003.1, 2004 says, among
> other things:
>
> * One of INF or INFINITY, ignoring case
>
> But MSVCRT is not entirely POSIX-compatible, so no big deal, we
> learn to live with its quirks.
Actually, this isn't a POSIX requirement, it's a ANSI/ISO C requirement.
(ISO/IEC 9899:1999 7.10.1.3.3).
But surely we're talking about the output of printf() and friends, not
the input accepted by strtod()?
B.
- References:
- [BUG]0/1=?, Linker
- Re: [BUG]0/1=?, Andy Armstrong
- Re: [BUG]0/1=?, David Kastrup
- Re: [BUG]0/1=?, Andy Armstrong
- Re: [BUG]0/1=?, Linker
- Re: [BUG]0/1=?, Peter Cawley
- Re: [BUG]0/1=?, Rob Kendrick
- Re: [BUG]0/1=?, Peter Cawley
- Re: [BUG]0/1=?, Rob Kendrick
- Re: [BUG]0/1=?, KHMan