[patch] libhal - allow NULLs for DBusError parameters

[John (J5) Palmieri]

On Tue, 2005-02-22 at 16:15 -0500, John (J5) Palmieri wrote:
> Most libhal methods now require an additional DBusError pointer to be
> passed into the method.  Sometimes errors are expected in a world where
> device can be added or removed at any moment.  These errors can be
> handled based on the return value of the method and do not need the
> extra verbosity that the dbus errors provide.  Attached is a patch which
> allows a NULL value to be passed to all methods which read HAL keys
> indicating that a dbus error is not needed thereby freeing the
> programmer from having to initialize and free dbus error objects when
> they are not needed.
> 
> _______________________________________________
> hal mailing list
> hal at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/hal

Don't use the other patch.  For some reason it has a regression in it
that cvs update doesn't seem to fix.  Here is the updated patch with the
reverted code stripped out.

-- 
John (J5) Palmieri
Associate Software Engineer
Desktop Group
Red Hat, Inc.
Blog: http://martianrock.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hal-allow-nulls-for-dbuserrors-2.patch
Type: text/x-patch
Size: 17380 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/hal/attachments/20050222/5946e32c/hal-allow-nulls-for-dbuserrors-2.bin
-------------- next part --------------
_______________________________________________
hal mailing list
hal at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/hal