I'm not sure what bits of mro are used in Dancer, but MRO::Compat may work as a drop-in replacement. From the documentation <https://metacpan.org/pod/MRO::Compat#DESCRIPTION>:
The "mro" namespace provides several utilities for dealing with method resolution order and method caching in general in Perl 5.9.5 and higher. This module provides those interfaces for earlier versions of Perl (back to 5.6.0 anyways). It is a harmless no-op to use this module on 5.9.5+. That is to say, code which properly uses MRO::Compat <http://search.cpan.org/%7Ebobtfish/MRO-Compat-0.12/lib/MRO/Compat.pm> will work unmodified on both older Perls and 5.9.5+. If you're writing a piece of software that would like to use the parts of 5.9.5+'s mro:: interfaces that are supported here, and you want compatibility with older Perls, this is the module for you. On Mon, Sep 15, 2014 at 1:01 PM, Warren Young <[email protected]> wrote: > A recent update to Dancer apparently introduced a requirement for the > 'mro' module, which is a Perl 5.10+ thing according to: > > http://search.cpan.org/~rjbs/perl-5.20.0/ext/mro/mro.pm > > I hope this can be fixed. One of the key reasons I chose Dancer is that > it still worked on Perl 5.8, which is what RHEL 5 shipped with, which will > still be in support for years: http://goo.gl/gUzmww > > It's too early to be dropping Perl 5.8, IMHO. Yes, I know, Modern Perl, > 12 years old, yadda yadda. Perl 5.8 was the current version for over 5 > years, so it got itself into a *lot* of places before 5.10 finally came > around to displace it. > _______________________________________________ > dancer-users mailing list > [email protected] > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users >
_______________________________________________ dancer-users mailing list [email protected] http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
