New DBus-related Compiler Warnings (Was: Re: Revision 596a5ae1df92802900f95e5b8a77006328dfc174)

Richard Laager rlaager at wiktel.com
Sat Jun 16 22:37:43 EDT 2007


On Sat, 2007-06-16 at 18:10 -0400, sadrul at pidgin.im wrote:
> -----------------------------------------------------------------
> Revision: 596a5ae1df92802900f95e5b8a77006328dfc174
> Ancestor: 346b2112f80fe533258dfed4af3ccf97aaa26a40
> Author: sadrul at pidgin.im
> Date: 2007-06-16T22:20:13
> Branch: im.pidgin.pidgin
> 
> Modified files:
>         libpurple/dbus-analyze-functions.py
> 
> ChangeLog: 
> 
> Treat some more types as simple types. This allows exporting some useful
> functions for dbus.
> Can this cause problems?

I *think* (but haven't tested) that this commit introduced these
warnings:

dbus-bindings.c: In function 'purple_conversation_set_data_DBUS':
dbus-bindings.c:3579: warning: passing argument 3 of 'purple_conversation_set_data' makes pointer from integer without a cast
dbus-bindings.c: In function 'purple_conversation_get_data_DBUS':
dbus-bindings.c:3596: warning: assignment makes integer from pointer without a cast
dbus-bindings.c: In function 'purple_core_quit_cb_DBUS':
dbus-bindings.c:4744: warning: passing argument 1 of 'purple_core_quit_cb' makes pointer from integer without a cast
dbus-bindings.c: In function 'purple_prefs_set_generic_DBUS':
dbus-bindings.c:6482: warning: passing argument 2 of 'purple_prefs_set_generic' makes pointer from integer without a cast

I think your later change introduced this:

dbus-bindings.c: In function 'purple_str_binary_to_ascii_DBUS':
dbus-bindings.c:9613: warning: pointer targets in passing argument 1 of 'purple_str_binary_to_ascii' differ in signedness

Richard
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://pidgin.im/pipermail/devel/attachments/20070616/fb10629a/attachment.sig>


More information about the Devel mailing list