You've already gotten lots of good explanations and answers. In your case, graff's node sounds like the best answer.

I just want to offer another suggestion for the general case.

What is the proper syntax for passing arguments to a subroutine that has a named reference when using callbacks?

You can use closures, as dank suggested; but you can do it without copying the whole subroutine body and you can make it general.

sub callback { my $coderef = shift; my @args = @_; sub { $coderef->(@args) } }

That will allow you to write things like

-command => callback($change_mode, 3),
but will work with any coderef (named or not) and arguments.

-sauoq
"My two cents aren't worth a dime.";

In reply to Re: Passing arguments to callback routines with named references by sauoq
in thread Passing arguments to callback routines with named references by nysus

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.