From: Alejandro Colomar <alx.manpages@gmail.com>
To: libc-alpha@sourceware.org
Cc: Alejandro Colomar <alx@kernel.org>
Subject: [PATCH v2 0/3] Add stpe*() functions
Date: Thu, 29 Dec 2022 00:17:39 +0100 [thread overview]
Message-ID: <20221228231741.125945-1-alx@kernel.org> (raw)
In-Reply-To: <20221222214217.1619716-1-alx@kernel.org>
Hi,
This version of the patch set adds the [v]stpeprintf() functions, which
are more necessary than stpecpy(3). snprintf(3) is the only way to
catenate formatted strings, and it's really bad for that.
stpecpy(3) has been optimized/reduced as much as I could.
Cheers,
Alex
Alejandro Colomar (3):
string: Add stpecpy()
stdio: Add vstpeprintf()
stdio: Add stpeprintf()
libio/Makefile | 4 +--
libio/stdio.h | 10 ++++++++
libio/vstpeprintf.c | 52 +++++++++++++++++++++++++++++++++++++++
stdio-common/Makefile | 1 +
stdio-common/stpeprintf.c | 32 ++++++++++++++++++++++++
string/Makefile | 1 +
string/stpecpy.c | 45 +++++++++++++++++++++++++++++++++
string/string.h | 7 ++++++
8 files changed, 150 insertions(+), 2 deletions(-)
create mode 100644 libio/vstpeprintf.c
create mode 100644 stdio-common/stpeprintf.c
create mode 100644 string/stpecpy.c
--
2.39.0
next prev parent reply other threads:[~2022-12-28 23:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 21:42 [PATCH 0/1] string: Add stpecpy(3) Alejandro Colomar
2022-12-22 21:42 ` [PATCH 1/1] " Alejandro Colomar
2022-12-23 7:02 ` Sam James
2022-12-23 12:26 ` Alejandro Colomar
2022-12-23 12:29 ` Alejandro Colomar
2022-12-23 17:21 ` Alejandro Colomar
2022-12-31 15:13 ` Sam James
2022-12-31 15:15 ` Alejandro Colomar
2022-12-28 23:17 ` Alejandro Colomar [this message]
2022-12-29 0:01 ` [PATCH v2 0/3] Add stpe*() functions Zack Weinberg
2022-12-29 10:13 ` Alejandro Colomar
2022-12-28 23:17 ` [PATCH v2 1/3] string: Add stpecpy() Alejandro Colomar
2022-12-28 23:27 ` Alejandro Colomar
2022-12-28 23:17 ` [PATCH v2 2/3] stdio: Add vstpeprintf() Alejandro Colomar
2022-12-28 23:17 ` [PATCH v2 3/3] stdio: Add stpeprintf() Alejandro Colomar
2022-12-28 23:27 ` 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=20221228231741.125945-1-alx@kernel.org \
--to=alx.manpages@gmail.com \
--cc=alx@kernel.org \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).