Re: speeding up XS_DBI_dispatch()

Tim Bunce <[email protected]>
Newsgroups gmane.comp.lang.perl.modules.dbi.sybase.devel
Message-ID <[email protected]>
On Tue, Feb 07, 2012 at 11:26:21PM +0000, Dave Mitchell wrote:
> On Tue, Feb 07, 2012 at 10:54:12PM +0000, Tim Bunce wrote:
> > > +# With this test code and threads, 5.8.1 has issues with freeing freed
> > > +# scalars, while 5.8.9 doesn't; I don't know about in-between - DAPM
> > 
> > "issues"? i.e., warnings at global destruction?
> 
> Yes, similar to those that t/35thrclone.t generates; i.e. I assume that
> it's a generic issue with ithreads in early 5.8.x releases (I remember
> fixing a lot of such issues, and Nicholas backporting them into
> maint-5.8). So I decided to just skip the threading-related cache tests
> for early 5.8.x's.

> I don't think the caching code is bringing up any new threading issues
> with early 5.8.x's; i.e. the new test file t/31methcache gives the same
> pattern of 'Attempt to free unreferenced scalar' warnings with or without
> the cache code.

Ah, okay. I'm happy to drop the "&& $] >= 5.008009" (which I did earlier)
so it'll run with 5.8.1+, and see what happens.

> PS - I'm currently working on bringing PERINTERP and DBIS into the
> Brave New World of MY_CXT.

Wonderful!

I presume that'll cause an API change that'll require compiled drivers
to be recompiled (ie. we'd bump DBISTATE_VERSION so check_version() will
croak).  It's been many years since a DBI upgrade has required that
(1998 as far as I can tell from the Changes file).

Tim.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.