Attachment 47933 Details for Bug 38285 – [PATCH 3/4] find_field_for_modification: document where the readers are left pointing

[patch] [PATCH 3/4] find_field_for_modification: document where the readers are left pointing

0003-find_field_for_modification-document-where-the-reade.patch (text/plain), 1.28 KB, created by Simon McVittie on 2011-06-14 02:34:51 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2011-06-14 02:34:51 UTC

Size: 1.28 KB

patch

obsolete

>From 72a3eef8181eb482dea2de14a49ac11ca3282801 Mon Sep 17 00:00:00 2001
>From: Simon McVittie <simon.mcvittie@collabora.co.uk>
>Date: Fri, 10 Jun 2011 10:39:10 +0100
>Subject: [PATCH 3/4] find_field_for_modification: document where the readers
> are left pointing
>
>---
> dbus/dbus-marshal-header.c |   13 +++++++++++++
> 1 files changed, 13 insertions(+), 0 deletions(-)
>
>diff --git a/dbus/dbus-marshal-header.c b/dbus/dbus-marshal-header.c
>index a6c9b80..9ff7c99 100644
>--- a/dbus/dbus-marshal-header.c
>+++ b/dbus/dbus-marshal-header.c
>@@ -1187,6 +1187,19 @@ _dbus_header_update_lengths (DBusHeader *header,
>                             header->byte_order);
> }
> 
>+/**
>+ * Try to find the given field.
>+ *
>+ * @param header the header
>+ * @param field the field code
>+ * @param reader a type reader; on success this is left pointing at the struct
>+ *  (uv) for the field, while on failure it is left pointing into empty space
>+ *  at the end of the header fields
>+ * @param realign_root another type reader; on success or failure it is left
>+ *  pointing to the beginning of the array of fields (i.e. the thing that might
>+ *  need realigning)
>+ * @returns #TRUE on success
>+ */
> static dbus_bool_t
> find_field_for_modification (DBusHeader     *header,
>                              int             field,
>-- 
>1.7.5.4
>

Actions: View | Splinter Review

Attachments on bug 38285: 47931 | 47932 | 47933 | 47934 | 51333

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.