From: Bruno Haible <bruno@clisp.org>
To: "Tim Rühsen" <tim.ruehsen@gmx.de>
Cc: bug-gnulib@gnu.org, ag <aga.chatzimanikas@gmail.com>
Subject: Re: string types
Date: Tue, 31 Dec 2019 10:53:59 +0100 [thread overview]
Message-ID: <7775995.zBxFH0rR4k@omega> (raw)
In-Reply-To: <82e3e796-f32d-3318-56e8-15c9e2cc2866@gmx.de>
Hi Tim,
> > - providing primitives for string allocation reduces the amount of buffer
> > overflow bugs that otherwise occur in this area. [1]
> > [1] https://lists.gnu.org/archive/html/bug-gnulib/2019-09/msg00031.html
> here is a string concatenation function without ellipsis, analogue to
> writev() and struct iovec - just a suggestion. Instead of 'struct
> strvec' a new string_t type would be handy.
>
> #include <stddef.h>
> #include <stdio.h>
> #include <stdlib.h>
> #include <string.h>
>
> struct strvec {
> char *strv_base;
> size_t strv_len;
> };
>
> __attribute__ ((nonnull (1)))
> char *concat_stringv(const struct strvec *strv)
> {
> const struct strvec *str;
> size_t len = 0;
> char *buf;
>
> for (str = strv; str->strv_base; str++)
> len += str->strv_len;
>
> if (!(buf = malloc(len + 1)))
> return buf;
>
> len = 0;
> for (str = strv; str->strv_base; len += str->strv_len, str++)
> memcpy(buf + len, str->strv_base, str->strv_len);
>
> buf[len] = 0;
>
> return buf;
> }
>
> void main(void)
> {
> char *s = concat_stringv((struct strvec []) {
> { "a", 1 },
> { "b", 1 },
> { NULL }
> });
This looks good. It brings us one step closer to the stated goal [1].
Would you like to contribute such a 'string-alloc' module that, together with
'strdup' and 'asprintf', removes most needs to create a string's contents
"by hand"?
Regarding the type name: There can't be a 'string_t' in C, I would say,
because you will always have the NUL-terminated strings on one side and what
you call a 'wget_string' on the other side, and there can't be a clear winner
between both.
Bruno
next prev parent reply other threads:[~2019-12-31 9:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 13:45 hard-locale: make multithread-safe Bruno Haible
2019-12-17 14:08 ` Tim Rühsen
[not found] ` <20191226221225.GA800@HATZ>
2019-12-27 10:51 ` string types Bruno Haible
2019-12-28 13:14 ` ag
2019-12-28 18:28 ` Paul Eggert
2019-12-28 20:44 ` ag
2019-12-28 22:40 ` Paul Eggert
2019-12-29 9:19 ` Bruno Haible
2019-12-29 17:13 ` ag
2019-12-29 20:02 ` ag
2019-12-29 21:24 ` Tim Rühsen
2019-12-31 9:53 ` Bruno Haible [this message]
2020-01-06 10:34 ` Tim Rühsen
2020-01-06 12:46 ` Bruno Haible
2020-01-06 16:08 ` Tim Rühsen
2020-01-06 16:49 ` Tim Rühsen
2019-12-18 1:45 ` hard-locale: make multithread-safe Paul Eggert
2019-12-18 8:51 ` Bruno Haible
2019-12-21 6:33 ` Bruno Haible
2019-12-18 10:29 ` LC_COLLATE in the C locale Bruno Haible
2019-12-18 16:27 ` Paul Eggert
2019-12-18 10:46 ` hard-locale: make multithread-safe Bruno Haible
2019-12-24 23:36 ` Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7775995.zBxFH0rR4k@omega \
--to=bruno@clisp.org \
--cc=aga.chatzimanikas@gmail.com \
--cc=bug-gnulib@gnu.org \
--cc=tim.ruehsen@gmx.de \
/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).