Around 23 o'clock on Feb 19, Matthieu Herrb wrote: > Given that setjmp/longjmp are not thread safe, wouldn't it be better > to have FreeType2 drop them in the future ?
FreeType2 is not a thread-safe library as far as I know, nor does the X server support threading either, but I'm not sure how a V7 or SYSV-style setjmp/longjmp wouldn't be thread safe (I realize BSD has horrid signal hacks added to setjmp, but that can be avoided in most systems by using the "pure" varient). FreeType2 actually moved *to* setjmp/longjmp and away from explicit exception handling at every layer of their library. I disagree with this, but I'm not going to refuse to use their otherwise useful library because of it. Feel free to tilt at this particular windmill if you like. > For the short term, makeing aliases for xf86setjmp/xf86longjump is > probably good enough. Even if the binary compat is broken, the need to > run a foreign OS font module is low, since they are open source. Binary compatibility will be gated only by the size of the jmp_buf; as long as the xf86jmp_buf is no smaller than the native jmp_buf, the aliases will provide precisely the same compatibility as is offered by the rest of the libc wrappers. -keith _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
