#include "unicode/utypes.h"
Go to the source code of this file.
Typedefs | |
typedef void * | UMTX |
An opaque pointer type that represents an ICU mutex. | |
typedef void U_CALLCONV | UMtxInitFn (const void *context, UMTX *mutex, UErrorCode *status) |
Function Pointer type for a user supplied mutex initialization function. | |
typedef void U_CALLCONV | UMtxFn (const void *context, UMTX *mutex) |
Function Pointer type for a user supplied mutex functions. | |
typedef int32_t U_CALLCONV | UMtxAtomicFn (const void *context, int32_t *p) |
Pointer type for a user supplied atomic increment or decrement function. | |
typedef void *U_CALLCONV | UMemAllocFn (const void *context, size_t size) |
Pointer type for a user supplied memory allocation function. | |
typedef void *U_CALLCONV | UMemReallocFn (const void *context, void *mem, size_t size) |
Pointer type for a user supplied memory re-allocation function. | |
typedef void U_CALLCONV | UMemFreeFn (const void *context, void *mem) |
Pointer type for a user supplied memory free function. | |
Functions | |
U_STABLE void | u_init (UErrorCode *status) |
Initialize ICU. | |
U_STABLE void | u_cleanup (void) |
Clean up the system resources, such as allocated memory or open files, used in all ICU libraries. | |
U_STABLE void | u_setMutexFunctions (const void *context, UMtxInitFn *init, UMtxFn *destroy, UMtxFn *lock, UMtxFn *unlock, UErrorCode *status) |
Set the functions that ICU will use for mutex operations Use of this function is optional; by default (without this function), ICU will directly access system functions for mutex operations This function can only be used when ICU is in an initial, unused state, before u_init() has been called. | |
U_STABLE void | u_setAtomicIncDecFunctions (const void *context, UMtxAtomicFn *inc, UMtxAtomicFn *dec, UErrorCode *status) |
Set the functions that ICU will use for atomic increment and decrement of int32_t values. | |
U_STABLE void | u_setMemoryFunctions (const void *context, UMemAllocFn *a, UMemReallocFn *r, UMemFreeFn *f, UErrorCode *status) |
Set the functions that ICU will use for memory allocation. |
Definition in file uclean.h.
|
Pointer type for a user supplied memory allocation function.
|
|
Pointer type for a user supplied memory free function. Behavior should be similar the standard C library free().
|
|
Pointer type for a user supplied memory re-allocation function.
|
|
An opaque pointer type that represents an ICU mutex. For user-implemented mutexes, the value will typically point to a struct or object that implements the mutex.
|
|
Pointer type for a user supplied atomic increment or decrement function.
|
|
Function Pointer type for a user supplied mutex functions. One of the user-supplied functions with this signature will be called by ICU whenever ICU needs to lock, unlock, or destroy a mutex.
|
|
Function Pointer type for a user supplied mutex initialization function. The user-supplied function will be called by ICU whenever ICU needs to create a new mutex. The function implementation should create a mutex, and store a pointer to something that uniquely identifies the mutex into the UMTX that is supplied as a paramter.
|
|
Clean up the system resources, such as allocated memory or open files, used in all ICU libraries. This will free/delete all memory owned by the ICU libraries, and return them to their original load state. All open ICU items (collators, resource bundles, converters, etc.) must be closed before calling this function, otherwise ICU may not free its allocated memory (e.g. close your converters and resource bundles before calling this function). Generally, this function should be called once just before an application exits. For applications that dynamically load and unload the ICU libraries (relatively uncommon), u_cleanup() should be called just before the library unload. u_cleanup() also clears any ICU heap functions, mutex functions or trace functions that may have been set for the process. This has the effect of restoring ICU to its initial condition, before any of these override functions were installed. Refer to u_setMemoryFunctions(), u_setMutexFunctions and utrace_setFunctions(). If ICU is to be reinitialized after after calling u_cleanup(), these runtime override functions will need to be set up again if they are still required. u_cleanup() is not thread safe. All other threads should stop using ICU before calling this function. Any open ICU items will be left in an undefined state by u_cleanup(), and any subsequent attempt to use such an item will give unpredictable results. After calling u_cleanup(), an application may continue to use ICU by calling u_init(). An application must invoke u_init() first from one single thread before allowing other threads call u_init(). All threads existing at the time of the first thread's call to u_init() must also call u_init() themselves before continuing with other ICU operations. The use of u_cleanup() just before an application terminates is optional, but it should be called only once for performance reasons. The primary benefit is to eliminate reports of memory or resource leaks originating in ICU code from the results generated by heap analysis tools. Use this function with great care!
|
|
Initialize ICU. The description further below applies to ICU 2.6 to ICU 3.4. Starting with ICU 3.4, u_init() needs not be called any more for ensuring thread safety, but it can give an indication for whether ICU can load its data. In ICU 3.4, it will try to load the converter alias table (cnvalias.icu) and give an error code if that fails. This may change in the future. For ensuring the availability of necessary data, an application should open the service objects (converters, collators, etc.) that it will use and check for error codes there. Documentation for ICU 2.6 to ICU 3.4: This function loads and initializes data items that are required internally by various ICU functions. Use of this explicit initialization is required in multi-threaded applications; in single threaded apps, use is optional, but incurs little additional cost, and is thus recommended. In multi-threaded applications, u_init() should be called in the main thread before starting additional threads, or, alternatively it can be called in each individual thread once, before other ICU functions are called in that thread. In this second scenario, the application must guarantee that the first call to u_init() happen without contention, in a single thread only.
If Extra, repeated, or otherwise unneeded calls to u_init() do no harm, other than taking a small amount of time.
|
|
Set the functions that ICU will use for atomic increment and decrement of int32_t values. Use of this function is optional; by default (without this function), ICU will use its own internal implementation of atomic increment/decrement. This function can only be used when ICU is in an initial, unused state, before u_init() has been called.
|
|
Set the functions that ICU will use for memory allocation. Use of this function is optional; by default (without this function), ICU will use the standard C library malloc() and free() functions. This function can only be used when ICU is in an initial, unused state, before u_init() has been called.
|
|
Set the functions that ICU will use for mutex operations Use of this function is optional; by default (without this function), ICU will directly access system functions for mutex operations This function can only be used when ICU is in an initial, unused state, before u_init() has been called. This function may be used even when ICU has been built without multi-threaded support (see ICU_USE_THREADS pre-processor variable, umutex.h)
|