From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: Archie Cobbs <archie.cobbs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk-manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Issue with asprintf()
Date: Mon, 11 May 2015 22:58:11 -0400 [thread overview]
Message-ID: <20150512025811.GA2965@vapier> (raw)
In-Reply-To: <CANSoFxs8XW6Z7ph2Uy1wFdeQPOGb7zvwJKExSLoUrMQ94b-8XA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
On 11 May 2015 17:46, Archie Cobbs wrote:
> There seems to be an issue with the asprintf() man page and underlying
> implementation (I'm using openSUSE 13.1 - man-pages-3.53).
>
> Since asprintf() is not POSIX, the man page effectively becomes the
> specification of its behavior.
not really. glibc specifies its behavior in its manual:
https://www.gnu.org/software/libc/manual/html_node/Dynamic-Output.html
any behavior not covered in the manual is unspecified. if you want to clarify
it, you should start with the glibc lists.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-12 2:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 22:46 Issue with asprintf() Archie Cobbs
[not found] ` <CANSoFxs8XW6Z7ph2Uy1wFdeQPOGb7zvwJKExSLoUrMQ94b-8XA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-12 2:58 ` Mike Frysinger [this message]
2015-05-12 5:17 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkjemzRg4OM02rQa2OLPU_EKJEDRcHWGpEFnNFvpkA02vQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-12 13:35 ` Archie Cobbs
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=20150512025811.GA2965@vapier \
--to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
--cc=archie.cobbs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk-manpages-Re5JQEeQqe8AvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.