NULL
68 * u_cleanup() also clears any ICU heap functions, mutex functions or 69 * trace functions that may have been set for the process. 70 * This has the effect of restoring ICU to its initial condition, before 71 * any of these override functions were installed. Refer to 72 * u_setMemoryFunctions(), u_setMutexFunctions and 73 * utrace_setFunctions(). If ICU is to be reinitialized after 74 * calling u_cleanup(), these runtime override functions will need to 75 * be set up again if they are still required. 76 *
77 * u_cleanup() is not thread safe. All other threads should stop using ICU 78 * before calling this function. 79 *
80 * Any open ICU items will be left in an undefined state by u_cleanup(), 81 * and any subsequent attempt to use such an item will give unpredictable 82 * results. 83 *
84 * After calling u_cleanup(), an application may continue to use ICU by 85 * calling u_init(). An application must invoke u_init() first from one single 86 * thread before allowing other threads call u_init(). All threads existing 87 * at the time of the first thread's call to u_init() must also call 88 * u_init() themselves before continuing with other ICU operations. 89 *
90 * The use of u_cleanup() just before an application terminates is optional, 91 * but it should be called only once for performance reasons. The primary 92 * benefit is to eliminate reports of memory or resource leaks originating 93 * in ICU code from the results generated by heap analysis tools. 94 *
95 * Use this function with great care! 96 *