Re: speeding up XS_DBI_dispatch()

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:
> > > 
> > > The DBI is always allowed to cheat in the name of performance!
> > > My simple but effective xsbypass hack doesn't seem to have caused
> > > problems in the years it's been there (though it's a pity threaded perls
> > > can't use it).
> > 
> > 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.

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.

Tim.