in reply to Re^8: Unusual sorting requirements; comparing three implementations.
in thread Unusual sorting requirements; comparing three implementations.
I'm not really sure what that lot is meant to tell me?
Class::XSAccessor is installed and where Moo (via Method::Generate::Accessor) should find it:
C:\test>perl -MClass::XSAccessor -mused -e1 C:/perl64/lib/Carp.pm : 1.11 C:/perl64/lib/Exporter.pm : 5.63 C:/perl64/lib/XSLoader.pm : 0.10 C:/perl64/lib/strict.pm : 1.04 C:/perl64/lib/warnings.pm : 1.06 C:/perl64/site/lib/Class/XSAccessor.pm : 1.13 C:/perl64/site/lib/Class/XSAccessor/Heavy.pm : N/A C:/perl64/site/lib/sitecustomize.pl : N/A C:/perl64/site/lib/used.pm : N/A C:\test>head -14 \perl64\site\lib\Method\Generate\Accessor.pm package Method::Generate::Accessor; use strictures 1; use Moo::_Utils; use base qw(Moo::Object); use Sub::Quote; use B 'perlstring'; BEGIN { our $CAN_HAZ_XS = !$ENV{MOO_XS_DISABLE} && _maybe_load_module('Class::XSAccessor') && (eval { Class::XSAccessor->VERSION('1.07') }) C:\test>
If it isn't, that's its bug; and quite frankly I have no interest is debugging over complicated and pointless modules I have no use for.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^10: Unusual sorting requirements; comparing three implementations.
by Anonymous Monk on Oct 25, 2012 at 08:06 UTC |