From: Eric Blake <eblake@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Markus Armbruster <armbru@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v2 00/14] QMP and QObject patches
Date: Wed, 28 Oct 2015 09:24:28 -0600 [thread overview]
Message-ID: <5630E8AC.4000900@redhat.com> (raw)
In-Reply-To: <CAFEAcA_xZzyvxEyQP-HwD=O9ujYD+NcNX-p3_CbMNxQigRysQw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]
On 10/28/2015 09:07 AM, Peter Maydell wrote:
>> glib: add compatibility interface for g_hash_table_add()
>> monitor: Turn monitor_qapi_event_state[] into a hash table
>
> CC qga/commands-posix.o
> In file included from /Users/pm215/src/qemu-for-merges/qga/main.c:25:
> In file included from
> /Users/pm215/src/qemu-for-merges/include/qapi/qmp/json-parser.h:17:
> In file included from /Users/pm215/src/qemu-for-merges/include/qemu-common.h:25:
> /Users/pm215/src/qemu-for-merges/include/glib-compat.h:171:12: error:
> returning 'void' from a function with incompatible result type
> 'gboolean' (aka 'int')
> return g_hash_table_replace(hash_table, key, key)
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Looks like g_hash_table_replace was originally a 'void' return
> and switched to 'gboolean' return at some later date:
>
> https://github.com/GNOME/glib/commit/910191597a6c2e5d5d460e9ce9efb4f47d9cc63c
This patch series isn't using the return value of g_hash_table_add, so
our glib replacement could be changed to return void.
On the other hand, would it be better to proactively retrofit the return
type into ALL of the g_hash_table_* functions that were swapped to
return a value, so that future uses of the functions with qemu can make
use of the modern contract, even though this series doesn't use it?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-10-28 15:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 8:15 [Qemu-devel] [PULL v2 00/14] QMP and QObject patches Markus Armbruster
2015-10-28 8:15 ` [Qemu-devel] [PULL v2 01/14] qobject: Drop QObject_HEAD Markus Armbruster
2015-10-28 8:15 ` [Qemu-devel] [PULL v2 02/14] qbool: Make conversion from QObject * accept null Markus Armbruster
2015-10-28 8:15 ` [Qemu-devel] [PULL v2 03/14] qdict: " Markus Armbruster
2015-10-28 8:15 ` [Qemu-devel] [PULL v2 04/14] qfloat qint: " Markus Armbruster
2015-10-28 8:15 ` [Qemu-devel] [PULL v2 05/14] qlist: " Markus Armbruster
2015-10-28 8:15 ` [Qemu-devel] [PULL v2 06/14] qstring: " Markus Armbruster
2015-10-28 8:15 ` [Qemu-devel] [PULL v2 07/14] monitor: Reduce casting of QAPI event QDict Markus Armbruster
2015-10-28 8:15 ` [Qemu-devel] [PULL v2 08/14] monitor: Simplify event throttling Markus Armbruster
2015-10-28 8:15 ` [Qemu-devel] [PULL v2 09/14] monitor: Switch from timer_new() to timer_new_ns() Markus Armbruster
2015-10-28 8:15 ` [Qemu-devel] [PULL v2 10/14] monitor: Split MonitorQAPIEventConf off MonitorQAPIEventState Markus Armbruster
2015-10-28 8:15 ` [Qemu-devel] [PULL v2 11/14] glib: add compatibility interface for g_hash_table_add() Markus Armbruster
2015-10-29 13:39 ` Markus Armbruster
2015-10-28 8:15 ` [Qemu-devel] [PULL v2 12/14] monitor: Turn monitor_qapi_event_state[] into a hash table Markus Armbruster
2015-10-28 8:16 ` [Qemu-devel] [PULL v2 13/14] monitor: Throttle event VSERPORT_CHANGE separately by "id" Markus Armbruster
2015-10-28 8:16 ` [Qemu-devel] [PULL v2 14/14] docs: Document QMP event rate limiting Markus Armbruster
2015-10-28 15:07 ` [Qemu-devel] [PULL v2 00/14] QMP and QObject patches Peter Maydell
2015-10-28 15:24 ` Eric Blake [this message]
2015-10-29 13:05 ` Markus Armbruster
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=5630E8AC.4000900@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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.