Appendix A Error codes

The values of type Perror_t are:

Name	Value	Meaning
`P_OK`	`0`	No error
`P_ERR`	`-1`	Some error

The values of type PerrCode_t are listed below. The “Has location” field indicates whether the parse descriptor contains a corresponding location in the source file.

Name	Has location	Meaning
`P_NOT_PARSED`	No	Data not yet parsed
`P_NO_ERR`	No	Value read, no error detected
`P_SKIPPED`	No
`P_UNEXPECTED_ERR`	No
`P_BAD_PARAM`	No
`P_SYS_ERR`	No
`P_IO_ERR`	No
`P_CHKPOINT_ERR`	No
`P_COMMIT_ERR`	No
`P_RESTORE_ERR`	No
`P_ALLOC_ERR`	No
`P_FORWARD_ERR`	No
`P_PANIC_SKIPPED`	No	Value skipped because of panic
`P_FMT_EMPTY_DELIM_ERR`	No
`P_INVALID_FUNCTION_CALL`	No
`P_SMART_NODE_ERR`	No	General error relating to smart nodes
`P_FAILWITH_ERR`	No	Error requiring an ocaml exception

Name	Has location	Meaning
`P_USER_CONSTRAINT_VIOLATION`	Yes
`P_MISSING_LITERAL`	Yes

`P_ARRAY_ELEM_ERR`	Yes
`P_ARRAY_SEP_ERR`	Yes
`P_ARRAY_TERM_ERR`	Yes
`P_ARRAY_SIZE_ERR`	Yes
`P_ARRAY_SEP_TERM_SAME_ERR`	Yes
`P_ARRAY_USER_CONSTRAINT_ERR`	Yes
`P_ARRAY_MIN_BIGGER_THAN_MAX_ERR`	Yes
`P_ARRAY_MIN_NEGATIVE`	Yes
`P_ARRAY_MAX_NEGATIVE`	Yes
`P_ARRAY_EXTRA_BEFORE_SEP`	Yes
`P_ARRAY_EXTRA_BEFORE_TERM`	Yes

`P_STRUCT_FIELD_ERR`	Yes
`P_STRUCT_EXTRA_BEFORE_SEP`	Yes
`P_UNION_MATCH_ERR`	Yes
`P_OPTION_MATCH_ERR`	Yes
`P_ENUM_MATCH_ERR`	Yes
`P_TYPEDEF_CONSTRAINT_ERR`	Yes

`P_AT_EOF`	Yes
`P_AT_EOR`	Yes
`P_EXTRA_BEFORE_EOR`	Yes
`P_EOF_BEFORE_EOR`	Yes
`P_COUNT_MAX_LIMIT`	Yes
`P_RANGE`	Yes

`P_INVALID_A_NUM`	Yes	Invalid ASCII number
`P_INVALID_E_NUM`	Yes	Invalid EBCDIC number
`P_INVALID_EBC_NUM`	Yes	Invalid EBC number
`P_INVALID_BCD_NUM`	Yes	Invalid BCD number

`P_INVALID_CHARSET`	Yes
`P_INVALID_WIDTH`	Yes

`P_CHAR_LIT_NOT_FOUND`	Yes
`P_STR_LIT_NOT_FOUND`	Yes
`P_REGEXP_NOT_FOUND`	Yes
`P_INVALID_REGEXP`	Yes
`P_WIDTH_NOT_AVAILABLE`	Yes
`P_INVALID_TIMESTAMP`	Yes
`P_INVALID_DATE`	Yes
`P_INVALID_TIME`	Yes
`P_INVALID_IP`	Yes
`P_INVALID_IP_RANGE`	Yes