62 #endif // WCSLIB_WCSLIB
3480 return wcs.err->status;
3483 In
this example,
if an error was generated in one of the
prjset() functions,
3484 wcsperr() would print an error traceback starting with
wcsset(), then
3485 celset(), and finally the particular projection-setting function that
3486 generated the error. For each of them it would print the status return value,
3487 function name, source file, line number, and an error message which may be
3488 more specific and informative than the general error messages reported in the
3489 first example. For example, in response to a deliberately generated error,
3490 the @c twcs test program, which tests
wcserr among other things, produces a
3491 traceback similar to this:
3493 ERROR 5 in
wcsset() at line 1564 of file wcs.c:
3494 Invalid parameter value.
3495 ERROR 2 in
celset() at line 196 of file cel.c:
3496 Invalid projection parameters.
3497 ERROR 2 in
bonset() at line 5727 of file prj.c:
3498 Invalid parameters for Bonne's projection.
3501 Each of the @ref structs "structs" in @ref overview "WCSLIB" includes a
3502 pointer, called @a err, to a
wcserr struct. When an error occurs, a struct is
3503 allocated and error information stored in it. The
wcserr pointers and the
3504 @ref memory "memory" allocated for them are managed by the routines that
3508 example above. If enabled, when an error occurs it is the user's
3509 responsibility to free the memory allocated for the error message using
3511 out of scope will result in memory leaks (if execution continues beyond the