> No, I was just busy doing other things.
>
> There is potentially one good reason to leave these changes in place for
> now: they allow proper thread cancellation in libc_r as it stands right
> now. This seems to me like a good enough reason to leave the changes as is
> until our grand new threads library is realized. However, I agree that in
> the end we will want to simplify the libc symbol naming.
>
> I'm planning on checking in libc_r cancellation changes today that use the
> current libc symbol naming setup. As soon as we're not using libc_r
> anymore I'll be glad to simplify the symbol naming.
I guess I'm confused as to why you can't do what you need with
_XXX (internally used, non-cancellable function) and XXX (weak
reference to _XXX) within libc. libc_r would provide XXX that
did something along the lines of:
int
XXX(void)
{
enter_cancellation_point();
_XXX();
leave_cancellation_point();
return(0);
}
Dan Eischen
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
