On Thu, May 03, 2001 at 06:03:09PM -0400, Dan Sugalski wrote:
> At 05:54 PM 5/3/2001 -0400, Benjamin Sugars wrote:
> >On Thu, 3 May 2001, Dan Sugalski wrote:
> >
> > > Nope. Callouts to non-reentrant libraries are a Bad Thing...
> >
> >I suppose all is not lost if one knows which Perl functions can trigger
> >such a callout, but that does fly in the face of Sarathy's responsibility
> >model.
>
> 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...)
>
> 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.
as well as licences, can we add CPAN sections for threadsafeness and
unicodesafeness, so module authors can declare if they know they have coded
to cope with them. [I can see a lot of "unknown"s turning up]
Nicholas Clark
