Eric Blake db3dd0824f maint: improve VIR_ERR_INVALID_CONN usage
The datatype.c object checks could result in a message like:

error: invalid connection pointer in no connection

This consolidates all clients of this message to have uniform contents:

error: invalid connection pointer in someFunc

Note that virCheckConnectReturn raises an error immediately; in
datatypes.c, where we don't need to raise the error (but instead
just leave it in the thread-local setting), we use
virCheckConnectGoto and the cleanup label instead.  Then, for
consistency in that file, all subsequent error messages are
touched to also use the cleanup error label.

* src/datatypes.h (virCheckConnectReturn)
(virCheckConnectGoto): New macros.
* src/datatypes.c: Use new macro.
* src/libvirt-qemu.c (virDomainQemuAttach): Likewise.
(virLibConnError): Delete unused macro.
* src/libvirt-lxc.c (virLibConnError): Likewise.
* src/libvirt.c: Use new macro throughout.
* docs/api_extension.html.in: Modernize documentation.

Signed-off-by: Eric Blake <eblake@redhat.com>
2014-01-06 21:41:02 -07:00
..
2013-12-02 10:21:26 +08:00
2013-12-02 10:21:26 +08:00
2013-12-02 11:59:18 -07:00
2013-12-02 10:21:26 +08:00
2013-12-02 10:21:26 +08:00
2013-12-02 10:21:26 +08:00
2013-12-02 12:17:51 +08:00
2013-12-02 10:21:26 +08:00
2013-09-12 17:18:32 +08:00
2013-11-26 18:37:09 +08:00
2013-12-02 10:21:26 +08:00