I think maybe I'm seeing the point you maybe were trying to get me to see.....the $$ prototype isn't really a limitation
Perhaps the point is that the $$ prototype can be a (confusing) limitation. For example:
use strict;
use warnings;
sub Fred($$)
{
my $arg1 = shift;
my $arg2 = shift;
print "arg1='$arg1'\n";
print "arg2='$arg2'\n";
}
my @two_elt_arr = ( 'abc', 'def' );
Fred(@two_elt_arr); # oops, compile error: "Not e
+nough arguments"
Fred($two_elt_arr[0], $two_elt_arr[1]); # this works
See
Modern Perl, "The Problem with Prototypes", page 242:
Prototype coercions work in subtle ways, such as enforcing scalar context on incoming arguments ... (examples elided) ... Those aren't even the subtler kinds of confusion you can get from prototypes.
