On Mon, 2009-09-21 at 08:59 +0100, Zhu, Yongsheng wrote: > > I'll think a bit about how this can be solved more elegantly without > > triggering the compiler bug. Extending the gdbus core so that it calls > > the C callbacks with two parameters (base pointer + per-callback data) > what are "base pointer" and 'per-callback data'?
I couldn't answer this without looking into the problem more thoroughly. The result is in the "gdbus-cxx" branch. This is still experimental. I need to split it up into smaller commits, want to set the ASYNC flag automatically (should be doable now), const members don't work yet, have to adapt SyncEvolution, ... But so far it looks promising. Lot's of horrible cut-and-paste code removed because asynchronous methods no longer require special treatment. No more manual writing of parameter lists. Signal names no longer duplicated. All memory freed (used to be stored in static structs). Global functions can be bound. -- 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. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
