Lines Matching refs:error
1 # Intl extension error conventions
3 The intl extension has particular conventions regarding error reporting. These
6 * The last error is always stored globally.
8 The global error code can be obtained in userland with `intl_get_error_code()`.
9 This is a `U_*` error code defined by ICU, but it does not have necessarily to
11 internal PHP wrapper functions can set these error codes when appropriate. For
13 the PHP wrapper function should set the global error code to
16 The error code (an integer) can be converter to the corresponding enum name
24 error occurred).
26 The internal PHP code can set the global last error with:
39 * The last is ALSO stored in the object whose method call triggered the error,
40 unless the error is due to bad arguments, in which case only the global error
53 The global error and the object error can be SIMULTANEOUSLY set with these
63 Node the extra `s` in the functions' names (`errors`, not `error`).
65 Static methods should only set the global error.
70 These methods are used to retrieve the error codes stored in the object's
74 * Intl methods and functions should return `FALSE` on error (even argument
82 * Intl functions and methods should reset the global error before doing anything
84 object's private error.
87 operates, where functions return immediately if an error is set.
92 void intl_error_reset(NULL); /* reset global error */
93 void intl_errors_reset(intl_error* err); /* reset global and object error */
101 way to reset the object's internal error code. Instead, resetting of the
102 object's internal error code is done upon fetching the object from its zval.
110 BREAKITER_METHOD_INIT_VARS; /* macro also resets global error */
122 BREAKITER_METHOD_FETCH_OBJECT; /* macro also resets object's error */
129 the object's error code.
