Re: [SyncEvolution] C++ D-Bus bindings + blocking calls
On Thu, 2012-02-16 at 14:15 +0100, Krzesimir Nowak wrote:
If I remember correctly then we have dbus_get_connection_fd()
function
that gets a connection pointer. In bluez wrapper connection pointer is
marked as DBusConnection and in GIO GDBus wrapper it is
GDBusConnection. But C++ intrusive pointer for them is
DBusConnectionPtr, so I decided then to change getConnection() methods
to return C++ pointer to have single name. I suppose I needed that
when I was updating GIO GDBus wrapper to bluez wrapper state. I guess
we need neither dbus_get_connection_fd() nor getConnection() returning
C++ pointer, so if I were you then I would just get rid of this
commit.
Right, I'll do. I think dbus_get_connection_fd() also became obsolete.
Sorry for being vague, but my memory on it already blurred. :)
I know exactly what you mean ;-) That's why I write detailed commit
messages, because I know that I cannot rely on my memory.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.