From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jonny Grant <jg-hus3n9K41k0@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: dlerror.3 query
Date: Sat, 26 Dec 2015 17:00:38 +0100 [thread overview]
Message-ID: <567EB9A6.5090606@gmail.com> (raw)
In-Reply-To: <5662DFBD.1090009-hus3n9K41k0@public.gmane.org>
On 12/05/2015 01:59 PM, Jonny Grant wrote:
> Hello
>
> Quoting from:
> http://man7.org/linux/man-pages/man3/dlerror.3.html
>
> "The dlerror() function returns a human-readable string describing the
> most recent error that occurred from a call to one of the functions
> in the dlopen API since the last call to dlerror(). The returned
> string does not include a trailing newline."
>
> My feeling is that this should say the string is null-terminated. Also I
> think it doesn't need to say it "does not include a trailing newline" -
> never seen that mentioned before, so probably no one would think it might.
I added the words "null-terminated" to the description, but I think
the mention that the string does not have a trailing newline does
no harm (and even POSIX has similar wording), so I left that in.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-12-26 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 12:59 dlerror.3 query Jonny Grant
[not found] ` <5662DFBD.1090009-hus3n9K41k0@public.gmane.org>
2015-12-26 16:00 ` Michael Kerrisk (man-pages) [this message]
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=567EB9A6.5090606@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=jg-hus3n9K41k0@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 NNTP newsgroup(s).