This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Patch to clean up extend.texi
- To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Subject: Re: Patch to clean up extend.texi
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Tue, 12 Jun 2001 13:02:51 +0200 (CEST)
- cc: <gcc-patches at gcc dot gnu dot org>
On Sun, 10 Jun 2001, Joseph S. Myers wrote:
> 2001-06-10 Joseph S. Myers <jsm28@cam.ac.uk>
>
> * gcc.texi: Change the font used for @def... commands to a fixed
> width font.
> * extend.texi: Use more logical markup. Use "built-in" instead of
> "builtin". Use @deftypefn to mark up built-in functions; specify
> their types in the @deftypefn and not in the descriptive text.
> Use TeX quotes and dashes. Add more index entries.
This looks good.
> -The following ISO C89 functions are recognized as builtins unless
> -@samp{-fno-builtin} is specified: @code{abs}, @code{cos}, @code{fabs},
> +The following ISO C89 functions are recognized as built-in functions unless
> +@option{-fno-builtin} is specified: @code{abs}, @code{cos}, @code{fabs},
One problem we now have, though, is that the name of the option
-fno-builtin does not match our "new" spelling of "built-in". Hmm.
> -pass up to @var{number} integer arguments in registers @var{EAX},
> -@var{EDX}, and @var{ECX} instead of on the stack. Functions that take a
> +pass up to @var{number} integer arguments in registers EAX,
> +EDX, and ECX instead of on the stack. Functions that take a
Agreed, yes.
> +@opindex fexternal-templates
> Add @samp{#pragma interface} to all files containing template
> definitions. For each of these files, add @samp{#pragma implementation
> "@var{filename}"} to the top of some @samp{.C} file which
> @samp{#include}s it.
Do we want to use @code instead of @samp here (and in the following
paragraph)?
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/