On Fri, May 07, 2004 at 10:09:10PM +0200, Leopold Toetsch wrote: > Nicholas Clark <[EMAIL PROTECTED]> wrote:
> > The PMC only used the PMC_data member to store a pointer on to a perl5 > > SV body. > > That's suboptimal :) Please have a look at the timings I posted a minute > ago. Stuff the pointer into PMC_struct_val(pmc) and get rid of the > C<need_ext> field in the pmc file. This will speed up things > considerable (~6 times) but, the question still remains - where are all > these live PMCs coming from. Does Ponie anchor everything so that > nothing gets collected? Thanks. >From skimming managedstruct.pmc I didn't realise that one could do this, let alone that it would be a superior approach. I think this illustrates quite nicely why I'd like documentation about PMCs I guess I'm going to have to write the first draft, based on the sources people have told me about. Nicholas Clark
