Date: Tue, 10 Dec 2002 22:41:36 +0300 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: djgpp-workers AT delorie DOT com Message-Id: <1438-Tue10Dec2002224135+0200-eliz@is.elta.co.il> X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9 In-reply-to: (rich AT phekda DOT freeserve DOT co DOT uk) Subject: Re: (C99) [PATCH] References: Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Tue, 10 Dec 2002 15:56:06 +0000 > From: "Richard Dawe" > > Please find below an implementation of 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.