develooper Front page | perl.perl5.porters | Postings from May 2016

Re: revert MG consting (Coro breakage) for 5.24?

Thread Previous | Thread Next
From:
Paul "LeoNerd" Evans
Date:
May 3, 2016 20:28
Subject:
Re: revert MG consting (Coro breakage) for 5.24?
Message ID:
20160503212257.37429fba@shy.leonerd.org.uk
On Tue, 3 May 2016 19:40:22 +0100
Nicholas Clark <nick@ccl4.org> wrote:

> > This should have relatively minimal effect (apart from 4K extra
> > memory usage per process), since all it would be doing is removing
> > a constraint on XS code (the vtable array can now be modified by XS
> > code again).  
> 
> So as best I can tell, all this achieves is a 4K increase in memory
> usage per process. It doesn't fix Coro. What's the upside?

It gives non-core CPAN module code the ability to mutate and change the
inner workings of perl core.

Isn't that what a lot of the more interesting hooks and features are
for? I occasionally find myself wanting some hook or ability and get a
little annoyed that there isn't one; but that's usually just down to
insufficient foresight for someone to have added it, or considerations
of the performance impact it would have (e.g. my desire to hook
SvREFCNT_dec). Intentionally removing a hook that has been demonstrated
to have use-cases seems a whole different thing.

-- 
Paul "LeoNerd" Evans

leonerd@leonerd.org.uk
http://www.leonerd.org.uk/  |  https://metacpan.org/author/PEVANS

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