develooper Front page | perl.perl5.porters | Postings from March 2015

Re: OP_SIGNATURE

Thread Previous | Thread Next
From:
Paul "LeoNerd" Evans
Date:
March 4, 2015 13:36
Subject:
Re: OP_SIGNATURE
Message ID:
20150304133557.2eabf4e4@shy.leonerd.org.uk
I'm very much with Zefram on this one.

Perl's core ops have always felt to me much like (Classic) Lego and UNIX
- a collection of lots of small well-intentioned pieces that fit
together in lots of interesting ways, increasing the power of the
collection as a whole because of it.

This proposed OP_SIGNATURE feels a lot like a very specialised piece
you'd find in a Star Wars Lego tie-in set. Very specifically-shaped for
exactly one job, and useless anywhere else.

If instead we can find a way to decompose the "signature" behaviour
into a few smaller, simpler ops, can we not find a way to implement
them just as efficiently, but now with greater flexibility to be able
to reuse those ops elsewhere, or in new combinations?

Arguments have been hand-waved in terms of performance. Has anyone
actually tried this though? Presumably the one big-shot OP_SIGNATURE is
going to itself do lots of things, and potentially be fairly slow in
itself because of that. Maybe this can be decomposed into pieces that
as a whole have more-or-less the same performance?

-- 
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