From: Alejandro Colomar <alx@kernel.org>
To: GIquadrat <ts@gi2.de>
Cc: linux-man@vger.kernel.org
Subject: Re: bug in signature of getnameinfo()
Date: Thu, 9 Apr 2026 21:49:02 +0200 [thread overview]
Message-ID: <adgCK_a_UVVMtMMS@debian> (raw)
In-Reply-To: <280D0348-17CF-4A16-87BC-18D884101324@gi2.de>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
Hi Thorsten,
On 2026-04-09T16:42:27+0200, GIquadrat wrote:
> Hi,
>
> https://www.man7.org/linux/man-pages/man3/getnameinfo.3.html
>
> shows a strange signature of getnameinfo:
>
> int getnameinfo(socklen_t hostlen, socklen_t servlen;
> const struct sockaddr *restrict addr, socklen_t addrlen,
> char host[_Nullable restrict hostlen],
> socklen_t hostlen,
> char serv[_Nullable restrict servlen],
> socklen_t servlen,
> int flags);
That's fine. You could try compiling it and you'll see it works as it
should. Just ignore everything before the ';' within the parameter
list (those are forward declarations of parameters).
That's documented in
<https://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html>.
Have a lovely night!
Alex
>
> Best regards
> Torsten
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
parent reply other threads:[~2026-04-09 19:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <280D0348-17CF-4A16-87BC-18D884101324@gi2.de>]
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=adgCK_a_UVVMtMMS@debian \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=ts@gi2.de \
/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