Hi Jakub,
On Fri, Apr 27, 2012 at 7:35 PM, Jakub Jelinek <jakub@xxxxxxxxxx> wrote:
> On Fri, Apr 27, 2012 at 03:59:58PM +1200, Michael Kerrisk (man-pages) wrote:
>> Gidday,
>>
>> I've written the man page page below to document glibc's
>> malloc_info(3). Review comments welcome!
>
> I think it would be nice to mention there that e.g. open_memstream (or
> fmemopen) could be used to store the XML output into a buffer in the
> program rather than into some file. IMHO that is quite common thing and
> thus could be hinted in the man page.
Thanks. I had a subtle hint on the page: SEE ALSO lists fmemopen(3).
But, your comment makes me think that it's better to be more explicit.
Under NOTES, I added
==
The
.BR open_memstream (3)
function can be used to send the output of
.BR malloc_info ()
directly into a buffer in memory, rather than to a file.
==
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Netdev]
[Linux Ethernet Bridging]
[Linux Wireless]
[Kernel Newbies]
[Memory]
[Security]
[Linux for Hams]
[Netfilter]
[Bugtraq]
[Photo]
[Yosemite]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux RAID]
[Linux Admin]
[Samba]
[Video 4 Linux]
[Linux Resources]