Re: [PATCH 5.005_62]Allow XS code to lock arbitrary scalars

Gurusamy Sarathy <gsar@ActiveState.com> wrote
> I can't make that judgement yet at this point, I want to wait to see
> how the other way fares first in comparison.  (My *guess* at this
> point would be that existing USE_THREADS will be out in the cold soon.)

I assume the "other way" is the use of perl_clone() ?

Is that approach capable of utilising multiple processors in parallel?


Mike Guy

• Re: [PATCH 5.005_62] Allow XS code to lock arbitrary scalars by Dan Sugalski
• [PATCH 5.005_62]Allow XS code to lock arbitrary scalars by Dan Sugalski
• Re: [PATCH 5.005_62]Allow XS code to lock arbitrary scalars by M.J.T. Guy
• Re: [PATCH 5.005_62]Allow XS code to lock arbitrary scalars by Gurusamy Sarathy
• Re: [PATCH 5.005_62]Allow XS code to lock arbitrary scalars by Dan Sugalski
• Re: [PATCH 5.005_62]Allow XS code to lock arbitrary scalars by Gurusamy Sarathy
• Re: [PATCH 5.005_62]Allow XS code to lock arbitrary scalars by Dan Sugalski
• Re: [PATCH 5.005_62]Allow XS code to lock arbitrary scalars by Booker Bense
• Re: [PATCH 5.005_62]Allow XS code to lock arbitrary scalars by Gurusamy Sarathy
• perl_clone (was Re: Allow XS code to lock arbitrary scalars) by Joshua N Pritikin
• Re: perl_clone (was Re: Allow XS code to lock arbitrary scalars) by Gurusamy Sarathy
• Re: [PATCH 5.005_62]Allow XS code to lock arbitrary scalars by Nick Ing-Simmons
• Re: [PATCH 5.005_62]Allow XS code to lock arbitrary scalars by Gurusamy Sarathy
• Re: [PATCH 5.005_62] Allow XS code to lock arbitrary scalars by Joshua N Pritikin