dbus-message: bring back the original layout of DBusMessageIter 35/231235/3 accepted/tizen/unified/20200421.051607 submit/tizen/20200420.123023 submit/tizen/20200420.213220
authorAdrian Szyndela <adrian.s@samsung.com>
Mon, 20 Apr 2020 09:35:42 +0000 (11:35 +0200)
committerAdrian Szyndela <adrian.s@samsung.com>
Mon, 20 Apr 2020 11:53:10 +0000 (13:53 +0200)
commit57bc36ad279e1363bd049afbe02b3d0a292dc0c8
tree7dcbf2d7f1c54ca9575861608382acf651d56bf7
parentcb35ffa24535d781f9cd1089aa4a1b049a75fffa
dbus-message: bring back the original layout of DBusMessageIter

The layout introduced with GVariant was kind of mimicking
the real structure, as opposed to the original layout, which
was taking into account only total sizes.

Dbus-1.10.8 introduced some static assertions for the properties of
DBusMessageIter. These are incompatible with the "GVariant" layout.

Moreover, they show that the "GVariant" layout could be prone to
the copying, that could omit some fields or parts of fields, due
to its not "packed" structure.

This commit brings back the original layout, with modifications
suited for GVariant-sized DBusMessageRealIter.

As an additional feature - this should fix compilation for 64-bit
architectures.

Change-Id: Ie1cac3748d408c22acf177ede5fb9e4e29818c9b
dbus/dbus-message.c
dbus/dbus-message.h