develooper Front page | perl.perl5.porters | Postings from June 2012

Re: whither PERL_[OLD_]COPY_ON_WRITE

Thread Previous | Thread Next
From:
Reini Urban
Date:
June 23, 2012 10:16
Subject:
Re: whither PERL_[OLD_]COPY_ON_WRITE
Message ID:
CAHiT=DEGedBJLnVWCKPTqB-Yor51g_Q-CgZOUpne=S_EdHnBZQ@mail.gmail.com
On Wed, Jun 20, 2012 at 11:53 AM, Father Chrysostomos <sprout@cpan.org> wrote:
> Dave Mitchell asked:
>> Whatever happened to PERL_COPY_ON_WRITE? Was it a failure? Should
>> it be expunged, or revived? Or left to rot?
>
> I asked the same question on the eleventh of December.  I am still
> awaiting a response.
>
> http://www.nntp.perl.org/group/perl.perl5.porters/;msgid=60396028-D993-4565-8EE9-3746ABB79C27@cpan.org

I don't think it was a failure. We have now shared strings for
bareword hash keys, files and stash names in strtab already.
The remaining problem as I see it, is how to apply that to the general
case for which strtab might not scale and be overkill.
And as Nick wrote, rewrite his old COW on top of those new shared hash keys.

I am also thinking of that in my typed/ro branch as readonly pad
strings can/should be shared.
I love Nick's approach.
If strings are const or typed then it would be safe. const would be
super safe, typed as string just much easier. But I'm not there yet.
-- 
Reini Urban
http://cpanel.net/   http://www.perl-compiler.org/

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About