Re: List::MoreUtils and require

Prototype and late loading don't run well together. Add XS into the mix, and you get a segfault instead of an error message. Bug? Anyway, workarounds for the original problem:

(1) Bypass prototype (ugly):

my $ea = &List::MoreUtils::each_array(\@v1, \@v2);

(2) Late compilation w/string eval (somewhat ugly, unnecessary compilation):

my $ea = eval q{ use List::MoreUtils; List::MoreUtils::each_array(@v1, @v2) };

(3) Declare the prototype yourself (might break(?) if List::MoreUtils upgrades behind your back):

sub List::MoreUtils::each_array(\@;\@\@\@\@\@\@\@\@\@\@\@\@\@\@\@\@\@\
+@\@\@\@\@\@\@);
my $ea = List::MoreUtils::each_array(@v1, @v2);
[download]

print "Just another Perl ${\(trickster and hacker)},"
The Sidhekin proves Sidhe did it!

Comment on Re: List::MoreUtils and require Select or Download Code

Replies are listed 'Best First'.
Re^2: List::MoreUtils and require by leriksen (Curate) on Jun 28, 2006 at 02:43 UTC
Could you also call import() after the require as a workaround ? `require List::MoreUtils; List::MoreUtils::import(); # or List::MoreUtils->import() ?` [download] ...reality must take precedence over public relations, for nature cannot be fooled. - R P Feynmann	[reply] [d/l]
Re^3: List::MoreUtils and require by Sidhekin (Priest) on Jun 28, 2006 at 02:56 UTC
Could you also call import() after the require as a workaround ? Not as such, since import just aliases the symbols in your own namespace. Doing that at runtime means it is too late to get the prototype checking. But ... ouch ... you could use that as a way to implicitly bypass prototype checking: `List::MoreUtils->import('each_array'); my $ea = each_array(\@v1, \@v2);` [download] I prefer being explicit when bypassing prototype checking though -- the flip side to not using that '&' sigil unless you mean it, is to make sure you do use it when you finally do mean it! `print "Just another Perl ${\(trickster and hacker)},"` The Sidhekin proves Sidhe did it!	[reply] [d/l] [select]