Mohammed Morsi
2008-Mar-31 20:31 UTC
[Ovirt-devel] [patch] Even Better Exceptions For ruby-libvirt bindings
I figured out how to add extra information to the exceptions, so from here on out we should be able to inform the client of whatever it needs to determine if it should continue processing. Right now, besides the standard message that ruby exceptions expect, the invoker's method_name" (previously just printed out) and "vir_connect_ptr" are added as attributes to the base ruby-libvirt exception. Enjoy! -------------- next part -------------- A non-text attachment was scrubbed... Name: _libvirt.c.patch Type: text/x-patch Size: 10499 bytes Desc: not available URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20080331/496324f4/attachment.bin>
Mohammed Morsi
2008-Mar-31 20:36 UTC
[Ovirt-devel] [patch] Even Better Exceptions For ruby-libvirt bindings
Mohammed Morsi wrote:> I figured out how to add extra information to the exceptions, so from > here on out we should be able to inform the client of whatever it > needs to determine if it should continue processing. Right now, > besides the standard message that ruby exceptions expect, the > invoker's method_name" (previously just printed out) and > "vir_connect_ptr" are added as attributes to the base ruby-libvirt > exception. Enjoy! > > > ------------------------------------------------------------------------ > > _______________________________________________ > Ovirt-devel mailing list > Ovirt-devel at redhat.com > https://www.redhat.com/mailman/listinfo/ovirt-develMy mistake, I ran "diff" manually, instead of "hg diff", attached is the corrected patch -------------- next part -------------- A non-text attachment was scrubbed... Name: _libvirt.c.patch Type: text/x-patch Size: 22568 bytes Desc: not available URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20080331/877cfcc9/attachment.bin>