On Fri, Jan 27, 2012 at 02:53:47PM +0000, Tim Bunce wrote:
> On Wed, Jan 25, 2012 at 08:17:27PM +0000, Tim Bunce wrote:
> > On Wed, Jan 25, 2012 at 04:14:07PM +0000, Dave Mitchell wrote:
> > > Just out of curiosity, why can't threaded perls use it?
> >
> > To be honest I can't remember now. It's disabled
> > #if (defined USE_THREADS || defined PERL_CAPI || defined PERL_OBJECT)
> > Can you think of a reason? All tests pass. Maybe I was just being
> > conservative.
>
> Ah, that's USE_THREADS not USE_ITHREADS. Ancient history.
Actually, USE_THREADS is normally also defined when USE_ITHREADS is
defined (the original USE_THREADS was renamed USE_5005THREADS).
> I've no idea what PERL_CAPI is. There's no reference to it in current
> perl headers and only a mention in Changes5.6: "Log: ensure XS_LOCKS
> stuff happens *before* XSUB is entered under -DPERL_CAPI"
> So I'll regard that as ancient history as well.
>
> As for PERL_OBJECT, I see that perl58delta.pod says "PERL_OBJECT has been
> completely removed." So that's yet more ancient history.
>
> So it seems that xsbypass is always enabled in 5.8+ builds.
So, I don't think its enabled, but it sounds like it could be.
--
The Enterprise's efficient long-range scanners detect a temporal vortex
distortion in good time, allowing it to be safely avoided via a minor
course correction.
-- Things That Never Happen in "Star Trek" #21
