All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3] stdio.3: note down fmemopen(3), fopencookie(3), and open_[w]memstream(3)
Date: Thu, 28 Dec 2023 20:06:14 +0100	[thread overview]
Message-ID: <ZY3HJ6w-rfG4MpgJ@debian> (raw)
In-Reply-To: <nn6xod4zdcimrh2pbhng4n7ff4x6g3pfjyb6u24swkno7thzx4@tarta.nabijaczleweli.xyz>

[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]

Hey,

On Tue, Dec 26, 2023 at 05:03:37PM +0100, наб wrote:
> I was looking for fmemopen to remember I was actually looking for
> open_memstream, and it was much more difficult than it ought to've been.
> 
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> ---
> Sorry for the v3 for some reason I didn't amend the commit
> (blame it on the holiday cheer).
> 
>  man3/stdio.3 | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/man3/stdio.3 b/man3/stdio.3
> index 833230402..0809b4536 100644
> --- a/man3/stdio.3
> +++ b/man3/stdio.3
> @@ -192,9 +192,15 @@ .SS List of functions
>  \fBfileno\fP(3)	T{
>  return the integer descriptor of the argument stream
>  T}
> +\fBfmemopen\fP(3)	T{
> +open memory as stream
> +T}
>  \fBfopen\fP(3)	T{
>  stream open functions
>  T}
> +\fBfopencookie\fP(3)	T{
> +opening a custom stream

Why use opening here, but open everywhere else?

Have a lovely Christmas!
Alex

> +T}
>  \fBfprintf\fP(3)	T{
>  formatted output conversion
>  T}
> @@ -243,6 +249,12 @@ .SS List of functions
>  \fBmktemp\fP(3)	T{
>  make temporary filename (unique)
>  T}
> +\fBopen_memstream\fP(3)	T{
> +open a dynamic memory buffer stream
> +T}
> +\fBopen_wmemstream\fP(3)	T{
> +open a dynamic memory buffer stream
> +T}
>  \fBperror\fP(3)	T{
>  system error messages
>  T}
> -- 
> 2.39.2



-- 
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-12-28 19:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-26 15:31 [PATCH] stdio.3: note down fmemopen(3) and fopencookie(3) наб
2023-12-26 16:02 ` [PATCH v2] stdio.3: note down fmemopen(3), fopencookie(3), and open_[w]memstream(3) наб
2023-12-26 16:03   ` [PATCH v3] " наб
2023-12-28 19:06     ` Alejandro Colomar [this message]
2023-12-28 19:28       ` наб
2023-12-28 20:10         ` Alejandro Colomar
2023-12-29 13:39           ` [PATCH] fopencookie.3, stdio.3: wfix наб
2023-12-29 13:52             ` Alejandro Colomar
2023-12-28 20:14     ` [PATCH v3] stdio.3: note down fmemopen(3), fopencookie(3), and open_[w]memstream(3) Alejandro Colomar

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=ZY3HJ6w-rfG4MpgJ@debian \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=nabijaczleweli@nabijaczleweli.xyz \
    /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.