From: Steven Sistare <steven.sistare@oracle.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael Roth" <michael.roth@amd.com>,
"Peter Xu" <peterx@redhat.com>, "Fabiano Rosas" <farosas@suse.de>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH V4 3/5] util: strv_from_strList
Date: Wed, 21 Feb 2024 12:01:39 -0500 [thread overview]
Message-ID: <67ba0f54-1bd7-4afc-80f5-1f4c4b1ad76c@oracle.com> (raw)
In-Reply-To: <87le7e3qoi.fsf@pond.sub.org>
On 2/21/2024 8:14 AM, Markus Armbruster wrote:
> Steve Sistare <steven.sistare@oracle.com> writes:
>
>> Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
>> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
>> ---
>> include/qemu/strList.h | 6 ++++++
>> util/strList.c | 14 ++++++++++++++
>> 2 files changed, 20 insertions(+)
>>
>> diff --git a/include/qemu/strList.h b/include/qemu/strList.h
>> index 010237f..4b86aa6 100644
>> --- a/include/qemu/strList.h
>> +++ b/include/qemu/strList.h
>> @@ -21,4 +21,10 @@
>> */
>> strList *strList_from_string(const char *in, const char *delim);
>>
>> +/*
>> + * Produce and return a NULL-terminated array of strings from @args.
>> + * The result is g_malloc'd and all strings are g_strdup'd.
>> + */
>> +GStrv strv_from_strList(const strList *args);
>> +
>> #endif
>> diff --git a/util/strList.c b/util/strList.c
>> index 7991de3..bad4187 100644
>> --- a/util/strList.c
>> +++ b/util/strList.c
>> @@ -22,3 +22,17 @@ strList *strList_from_string(const char *str, const char *delim)
>>
>> return res;
>> }
>> +
>> +GStrv strv_from_strList(const strList *args)
>
> Suggest to name the argument @list.
>
>> +{
>> + const strList *arg;
>
> Suggest to name this @tail.
ok.
>> + int i = 0;
>> + GStrv argv = g_new(char *, QAPI_LIST_LENGTH(args) + 1);
>> +
>> + for (arg = args; arg != NULL; arg = arg->next) {
>> + argv[i++] = g_strdup(arg->value);
>> + }
>> + argv[i] = NULL;
>> +
>> + return argv;
>> +}
>
> Can we use char ** instread of GStrv? I'd find that clearer. For what
> it's worth, GLib documentation of functions like g_strsplit() doesn't
> use the GStrv typedef, either.
ok.
- Steve
next prev parent reply other threads:[~2024-02-21 17:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 22:49 [PATCH V4 0/5] string list functions Steve Sistare
2024-01-12 22:49 ` [PATCH V4 1/5] util: strList_from_string Steve Sistare
2024-02-21 13:29 ` Markus Armbruster
2024-02-21 17:01 ` Steven Sistare
2024-02-22 19:46 ` Steven Sistare
2024-01-12 22:49 ` [PATCH V4 2/5] qapi: QAPI_LIST_LENGTH Steve Sistare
2024-02-21 13:29 ` Markus Armbruster
2024-02-21 17:01 ` Steven Sistare
2024-01-12 22:49 ` [PATCH V4 3/5] util: strv_from_strList Steve Sistare
2024-02-21 13:14 ` Markus Armbruster
2024-02-21 17:01 ` Steven Sistare [this message]
2024-01-12 22:49 ` [PATCH V4 4/5] util: strList unit tests Steve Sistare
2024-02-21 13:19 ` Markus Armbruster
2024-02-21 17:01 ` Steven Sistare
2024-01-12 22:49 ` [PATCH V4 5/5] migration: simplify exec migration functions Steve Sistare
2024-02-21 13:10 ` Markus Armbruster
2024-02-21 13:55 ` Fabiano Rosas
2024-02-21 15:54 ` Fabiano Rosas
2024-02-21 17:01 ` Steven Sistare
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=67ba0f54-1bd7-4afc-80f5-1f4c4b1ad76c@oracle.com \
--to=steven.sistare@oracle.com \
--cc=armbru@redhat.com \
--cc=farosas@suse.de \
--cc=marcandre.lureau@redhat.com \
--cc=michael.roth@amd.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).