I would recommend using (&@) as a prototype. That way you can use a list for other arguments. If you use ($\@) your second argument must be an array. 
use strict;
use  Data::Dumper;
sub takes_coderef (&@);

takes_coderef {print "I'm a code ref called with (", join(", ", @_), "
+)\n"} "first", 2, 3;

sub takes_coderef (&@) {
    my $coderef = shift;
    my @otherargs = @_;
    &$coderef(@otherargs);
    print Data::Dumper->Dump([\@otherargs], ["*otherargs"]);
}
___OUTPUT___
I'm a code ref called with (first, 2, 3)
@otherargs = (
               'first',
               2,
               3
             );

[download]
See this thread about prototypes and especially Tom Christiansen's Prototypes in Perl for a very in-depth discussion of prototypes.

--

flounder

In reply to Re: Re: Creating operators in the flavor of map & grep... by flounder99
in thread Creating operators in the flavor of map & grep... by cluka

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.