Mail Archives: djgpp-workers/2002/12/10/15:42:52
> Date: Tue, 10 Dec 2002 15:56:06 +0000
> From: "Richard Dawe" <rich AT phekda DOT freeserve DOT co DOT uk>
>
> Please find below an implementation of <inttypes.h> and all its functions.
Thanks!
> --- 794,811 ----
>
> @findex _doprnt AT r{, and }hh AT r{ conversion qualifier}
> @findex printf AT r{, and }hh AT r{ conversion qualifier}
> ! @findex _doscan AT r{, and }hh AT r{ conversion qualifier}
> ! @findex scanf AT r{, and }hh AT r{ conversion qualifier}
> ! The @code{hh} conversion qualifier is now supported by @code{_doprnt},
> ! @code{_doscan}, the @code{printf} family of functions
> ! and the @code{scanf} family of functions.
This part belongs to another patch, it seems.
> + intmax_t imaxabs (intmax_t x);
> + @end example
> +
> + @subheading Description
> +
> + This function takes the absolute value of @var{x}. @xref{abs}.
Shouldn't we explain why do we need another function that does what
`abs' does?
> + @subheading Return Value
> +
> + |@var{x}|
I'd suggest @code{|@var{x}|} instead, it will look better in print.
> + @item PRIoFASTN
> + @itemx PRIuFASTN
> + @itemx PRIxFASTN
> + @itemx PRIXFASTN
> +
> + The @code{o}, @code{u}, @code{x} and @code{X} type conversion specifiers
> + for a type @code{uint_FASTN_t} of N bits.
I suggest to use @var{N} in both @item's and the text below them. N
stands for a number here, right?
Finally, there are a few places where there's only one blank after a
period that ends a sentence, instead of two blanks.
- Raw text -