1: the team gets very familiar with APR 2: the team gets very familiar with Perl internals 3: Perl (the language) gets abstracted away from Perl (the compatibility layer)
I'm not sure if any of those meet the "besides" criterion. On Wed, Sep 11, 2013 at 11:31 PM, Teal <[email protected]> wrote: > What would the advantages be? > Besides sheer geek bravado display :) > > Teal > > > Anyone for creating a fork of Perl that uses APR for platform abstraction > (instead of native Perl platform abstraction?) > > > > -- > You've got to wiggle before you can crawl > > > _______________________________________________ > kc mailing [email protected]http://mail.pm.org/mailman/listinfo/kc > > > > _______________________________________________ > kc mailing list > [email protected] > http://mail.pm.org/mailman/listinfo/kc > -- You've got to wiggle before you can crawl
_______________________________________________ kc mailing list [email protected] http://mail.pm.org/mailman/listinfo/kc
