On Mon, 2012-02-13 at 14:50 +0100, Chris Kühl wrote: > - Krzesimir implemented the missing functionality in the gio-gdbus > wrapper and added code to do blocking calls with minimal extra code > required in consuming classes.
In addition to adding a block() method which executes the call, wouldn't it be nicer to also overload the call operator such that if there is no Callback_t parameter, all results are returned directly (special case for a single return value) or as tuple (general case)? The block() call would be more efficient for large return values (avoids one copying), but for small ones the ease of use certainly would be worth it. I've experimented a bit with it and think it can be done. Is there still a need for the block() variant if there was a "normal" blocking call operator()? -- 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
