On 11/04/12 09:06, Irek Szczesniak wrote: > This is useless because you still do not have newlocale(), duplocale() > or uselocale() which create or use the locale_t object.
Those can be dummied out as well. > The point of the new apis is that you can have an unlimited number of > locale_t objects, all with different properties. As side effect > different threads can use different locale_t objects, giving threads > the ability to run in different locales. But this feature is NOT > limited to per-thread locales as some people may think. I think the underlying point that the previous poster was making was that for a significant number of users, the desktop environment is launched with the per-process locale set correctly, and the user happily spends all of his time in that single locale. Being able to switch locales on a thread-by-thread basis is certainly nifty, and is perhaps useful in some service providing scenarios (e.g., a web server), but it's quite unclear at least to me how it'd be very much helpful to build a window manager. Perhaps there are multi-lingual people who really do need to have a window manager that can decorate each window differently ... but really? -- James Carlson 42.703N 71.076W <[email protected]> _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
