C question (was Re: [mp2] Our API is not perl thread-safe)

2005-03-27 Thread Stas Bekman
We will now have to replace all wrappers like: #define mp_xs_APR__Pool_2obj(ptr) \ sv_setref_pv(sv_newmortal(), "APR::Pool", (void*)ptr) with an additional call to this macro #define MP_CLONE_INSERT_OBJ(namespace, obj) \ {

Re: Test.pm can't deal with ithreads, need Test::More

2005-03-27 Thread Stas Bekman
Geoffrey Young wrote: Stas Bekman wrote: As we start adding tests running in ithreads, we no longer can use Test.pm, which can't deal with the test counter. when several threads print 'ok 1' we get: ok 136 Test output counter mismatch [test 277] since in each thread, Test.pm's counter has a differe

Re: Test.pm can't deal with ithreads, need Test::More

2005-03-27 Thread Stas Bekman
Adam Kennedy wrote: It's common practise for dists that need bleeding edge versions of Test::... modules (or other things that are build-time and not run-time dependencies) to /inc'lude them in the distribution but not need to install them. That's a good idea, Adam. Not sure how many other prere

Re: [mp2] Our API is not perl thread-safe

2005-03-27 Thread Stas Bekman
Stas Bekman wrote: Have done some good but painfully slow progress, now partially covering APR::Table and APR::Pool. In case you care to look here is the work in progress. I wonder if I should branch that since there are going to be *a lot* of additions if this ever works. My main obstacle at t

Re: Test.pm can't deal with ithreads, need Test::More

2005-03-27 Thread Geoffrey Young
Stas Bekman wrote: > As we start adding tests running in ithreads, we no longer can use > Test.pm, which can't deal with the test counter. when several threads > print 'ok 1' we get: > > ok 136 > Test output counter mismatch [test 277] > > since in each thread, Test.pm's counter has a different

Re: [VOTE] s/Apache::/Apache2::/g

2005-03-27 Thread Joe Schaefer
Stas Bekman <[EMAIL PROTECTED]> writes: [...] > OK, so you clearly win. surprise, surprise :) I'd like to make a few observations at this point. Don't feel bad about how this all worked out. The bug was a community bug, and this community seems more than willing to do its part to correc