Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
Joe Schaefer wrote:
[...]
I'm talking to p5p at the moment trying to figure a way to do minimal
copying. Next I could change the modperl SV bucket struct to have a pv
pointer in addition to an sv pointer. The pv pointer will point to
PVX(sv) in case when sv wasn't copied, and it'll contain a sole copy
of PVX(sv) in case it had to be copied and sv = Nullsv. When the
bucket is freed either the sv is freed or the pv is freed
(automatically). The culprit is it'll require a pool argument,
which complicates things. So may be I'll just do a plain sv copy.
^^^^^^^^^^^^^
+1.
It would certainly require some planning efforts to coordinate
everything, but I believe it's possible to do something like this.
What planning efforts do you refer to?
I meant cordinating actions on the sv (copy, modify, reassign)
with actions on the bucket (setaside). It's probably not worth
the extra effort, though, so I agree that copying the string
might be the best thing to do.
Yes, but only when we have to. Otherwise it'll be *very* wasteful and slow.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
