table of contents
other versions
- wheezy 0.7.3-6
- jessie 0.7.3-6+b2
- testing 0.9.4-1
- unstable 0.9.4-1
- experimental 0.10.0-1
gd_validate(3) | GETDATA | gd_validate(3) |
NAME¶
gd_validate — check a dirfile field code for validitySYNOPSIS¶
#include <getdata.h>int
gd_validate(DIRFILE *dirfile, const char
*field_code);
DESCRIPTION¶
The gd_validate() function queries a dirfile(5) database specified by dirfile and checks whether field_code, which may contain a representation suffix, specifies a valid field.RETURN VALUE¶
If all checks pass, gd_validate() returns zero. On error, it returns -1 and sets the dirfile error to a non-zero error value. Possible error values are:- GD_E_BAD_CODE
- The field specified by field_code or one of the fields it uses as input was not found in the database.
- GD_E_BAD_DIRFILE
- The supplied dirfile was invalid.
- GD_E_BAD_REPR
- The representation suffix specified in field_code was not recognised.
- GD_E_BAD_SCALAR
- A non-literal scalar used in the definition of the field or one of its inputs was not found, or was not a CONST or CARRAY field.
- GD_E_DIMENSION
- A scalar field was found where a vector field was expected.
- GD_E_RECURSE_LEVEL
- Too many levels of recursion were encountered while trying to resolve field_code. This usually indicates a circular dependency in field specification in the dirfile.
NOTES¶
It is not necessary to call this function before passing a field code to another GetData function: all functions which accept field codes perform these checks themselves.SEE ALSO¶
dirfile(5), gd_getdata(3), gd_error(3), gd_error_string(3), gd_open(3)3 November 2010 | Version 0.7.0 |