On Thu, 3 May 2001, Dan Sugalski wrote:

> Well, presumably they'll only happen in XS code and the author will take 
> proper steps to protect the library. (Okay, you can stop laughing now...)

I was thinking more about getpwuid and friends rather than XS code.

> Seriously, there's not a whole lot that perl itself can do about that, 
> except perhaps single-thread calls to XS routines that aren't guaranteed to 
> be threadsafe. And that needs to be done across interpreters for IThreads.

So -- by extension -- should threaded Perl acquire a lock before entering
getpwuid?  Or should it call the getpwuid_r hack if its available?  Or
should the PODs be stuffed full of thread-safeness disclaimers?

Cheers,
-Ben

-- 
signer: can't create ~/.sig: Socket type not supported

Reply via email to