public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [COMMITTED] manual: Fix strerrorname_np and strerrordesc_np return type (BZ #26343)
Date: Fri, 07 Aug 2020 22:04:45 +0200	[thread overview]
Message-ID: <871rki5ijm.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20200807195230.3312135-1-adhemerval.zanella@linaro.org> (Adhemerval Zanella via Libc-alpha's message of "Fri, 7 Aug 2020 16:52:30 -0300")

* Adhemerval Zanella via Libc-alpha:

> ---
>  manual/errno.texi | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/manual/errno.texi b/manual/errno.texi
> index 6ca566522d..7ac1554bb1 100644
> --- a/manual/errno.texi
> +++ b/manual/errno.texi
> @@ -1207,7 +1207,7 @@ to @code{errno}.
>  The function @code{perror} is declared in @file{stdio.h}.
>  @end deftypefun
>  
> -@deftypefun void strerrorname_np (int @var{errnum})
> +@deftypefun const char * strerrorname_np (int @var{errnum})
>  @standards{GNU, string.h}
>  @safety{@mtsafe{}@assafe{}@acsafe{}}
>  This function returns the name describing the error @var{errnum} or
> @@ -1218,7 +1218,7 @@ for @code{EINVAL}).
>  This function is a GNU extension, declared in the header file @file{string.h}.
>  @end deftypefun
>  
> -@deftypefun void strerrordesc_np (int @var{errnum})
> +@deftypefun const char * strerrordesc_np (int @var{errnum})
>  @standards{GNU, string.h}
>  @safety{@mtsafe{}@assafe{}@acsafe{}}
>  This function returns the message describing the error @var{errnum} or

You need to put the return type in braces because it's not a single
identifier: {const char *}

Otherwise it's not rendered or indexed correctly.

  reply	other threads:[~2020-08-07 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-07 19:52 Adhemerval Zanella
2020-08-07 20:04 ` Florian Weimer [this message]
2020-08-07 20:17   ` Adhemerval Zanella
2020-08-07 20:31     ` Florian Weimer
2020-08-08 19:53       ` Adhemerval Zanella

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871rki5ijm.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).