No next::method 'new' found for SQL::Abstract::More

[pjlsergeant]

# Works on 5.30.2, fails on 5.16.3
# No next::method 'new' found for SQL::Abstract::More at /Users/pjlsergeant/perl5/perlbrew/perls/perl-5.16.3/lib/5.16.3/darwin-2level/mro.pm line 27.

use Module::Runtime;
Module::Runtime::require_module('SQL::Abstract::More');
my $s = SQL::Abstract::More->new();

[damil]

strange ... CPAN testers has no failure report for 5.16.3 (http://matrix.cpantesters.org/?dist=SQL-Abstract-More%201.37;perl=5.16.3;reports=1)

Can you please supply the full list of module versions in your environment ? Most probably the problem is due to a specific version of mro or of SQL::Abstract.

[pjlsergeant]

Are any of the CPAN testers loading the module with Module::Runtime?

SQL::Abstract 2.000001
SQL::Abstract::More 1.37
mro 1.09
MRO::Compat 0.13

[damil]

Got it.

This is because Module::Runtime::require_module(..) does not call import(). SQL::Abstract::More needs a call to import() because this is where the inheritance hierarchy is set up (this is because there is a compatibility layer to support both SQL::Abstract or SQL::Abstract::Classic as parents).

So if you replace "require" by "use", or if you add a call to ->import() in your code, it should work.

[shadowcat-mst]

Whether you prefer SQL::Abstract 2 or SQL::Abstract::Classic as parent you really should put one of them into @isa to begin with.

Overwriting @isa works fine for perl in general - so I'd suggest taking line 30 (from https://metacpan.org/release/SQL-Abstract-More/source/lib/SQL/Abstract/More.pm ) and merging it into line 24 and then letting your import override as required.

If you want to avoid confusion, I'd add a flag in your new() method that throws an error is things have been reconfigured after the creation of the first object.

[damil]

Hi mst. Good points, thanks for the suggestions, I will follow them.

[pjlsergeant]

It's a little weird that it works on 5.30.2, fails on 5.16.3