[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gcc-patches
Subject:    Re: Patch:  nested function doc
From:       Geoffrey Keating <geoffk () geoffk ! org>
Date:       2005-01-31 21:36:40
Message-ID: m2zmyp8emv.fsf () greed ! local
[Download RAW message or body]

Dale Johannesen <dalej@apple.com> writes:

> While dealing with an unhappy user Geoff and I noticed the
> documentation for inline
> functions was wrong; they do not have internal linkage.  Also
> clarifies that "static"
> is not allowed.  Bootstrapped and 'info' eyeballed.  OK?
> 
> 2005-01-30  Dale Johannesen  <dalej@apple.com>
> 
>          * doc/extend.texi (nested functions):  Fix linkage description.
>          Clarify that static is not allowed.

This is OK.

> Index: extend.texi
> ===================================================================
> RCS file: /cvs/gcc/gcc/gcc/doc/extend.texi,v
> retrieving revision 1.235
> diff -u -d -b -w -p -r1.235 extend.texi
> --- extend.texi 3 Dec 2004 17:37:09 -0000       1.235
> +++ extend.texi 31 Jan 2005 02:26:45 -0000
> @@ -449,8 +449,8 @@ bar (int *array, int offset, int size)
>   @end group
>   @end smallexample
> 
> -A nested function always has internal linkage.  Declaring one with
> -@code{extern} is erroneous.  If you need to declare the nested function
> +A nested function always has no linkage.  Declaring one with
> +@code{extern} or @code{static} is erroneous.  If you need to declare
> the nested function
>   before its definition, use @code{auto} (which is otherwise meaningless
>   for function declarations).
[prev in list] [next in list] [prev in thread] [next in thread]