| 43 |
|
<void/> |
| 44 |
|
</funcprototype> |
| 45 |
|
<funcprototype> |
| 46 |
+ |
<funcdef>int<function>sg_get_error_errno</function></funcdef> |
| 47 |
+ |
<void/> |
| 48 |
+ |
</funcprototype> |
| 49 |
+ |
<funcprototype> |
| 50 |
|
<funcdef>const char *<function>sg_str_error</function></funcdef> |
| 51 |
|
<paramdef>sg_error <parameter>code</parameter></paramdef> |
| 52 |
|
</funcprototype> |
| 165 |
|
The first, <function>sg_get_error</function> returns an sg_error code |
| 166 |
|
which relates to the last error generated by libstatgrab. This can be |
| 167 |
|
converted to a string by calling <function>sg_str_error</function> |
| 168 |
< |
giving the sg_error code as an argument. Finally, an optional |
| 168 |
> |
giving the sg_error code as an argument. An optional |
| 169 |
|
argument may be set when the error was generated. This can be |
| 170 |
< |
accessed by calling <function>sg_get_error_arg</function>. |
| 170 |
> |
accessed by calling <function>sg_get_error_arg</function>; |
| 171 |
> |
<constant>NULL</constant> will be returned if no argument has |
| 172 |
> |
been set. Some errors will also record the value of the system |
| 173 |
> |
errno variable when the error occurred; this can be retrieved by |
| 174 |
> |
calling <function>sg_get_error_errno</function>, which will |
| 175 |
> |
return <constant>0</constant> if no valid errno has been recorded. |
| 176 |
|
</para> |
| 177 |
|
<para> |
| 178 |
|
It is the intended practice that whenever a libstatgrab function is |
