Mail Archives: djgpp-workers/2003/03/18/16:21:27
> From: <ams AT ludd DOT luth DOT se>
> Date: Tue, 18 Mar 2003 21:03:36 +0100 (CET)
>
> This function converts as many characters of @var{s} as look like a
> -floating point number into that number. If @var{endp} is not a null
> +floating point number into that number. It also recognises
> +(case-insensitivly) @code{Inf}, @code{Infinity}, @code{NaN} and
> +@code{NaN(<optional integer>)}. If @var{endp} is not a null
The "<optional integer>" part should be "@var{optional integer}",
since it stands for something else, i.e. it's a meta-syntactic
variable.
> +If @var{s} is @code{Inf} or @code{Infinity}, with any variations of
I think that it's better to use ``Inf'', ``Infinity'', ``NaN'',
etc. when you mean literal strings, since they are not symbols in this
context. @code{Inf} is for when you talk about an infinite value.
> +If @var{s} is @code{NaN(<integer>)}, with any variations of
"<integer>" should be "@var{integer}".
Btw, do we really intend to support non-hex values here?
> +@code{<integer>&0xfffffffffffff} is 0 (which is won't work as a
There's a typo here: "is won't work".
- Raw text -