On Tue, 2008-01-08 at 22:12 +0100, Ole André Vadla Ravnås wrote:
> If the Python code throws an exception during an inbound D-Bus method
> call it will be marshalled into a D-Bus exception, which, depending on
> the client's D-Bus bindings, ends up as an error or exception there.
> For the C/GLib D-Bus bindings the function returns FALSE and the last
> parameter, a GError **, receives a pointer to a newly allocated GError
> (no C++ exception, just an innocent return value along with a
> descriptive error name and description). And if it's a different
> language/bindings, say C#, you get an appropriate Exception thrown.
>
I tend to use the low level dbus interface from C to avoid generating a
dependency on a third party library such as glib - so I will have to
investigate how the Python exception is handled at this layer. However I
have never handled communication between C and Python before so thanks
for that info - it will save me some work!
John.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
