No need for globals, just have the coderef use lexicals in the scope it's declared in (i.e. use a closure).
{
my $returned_data = [ ];
sub my_fetch_callback { push @{ $returned_data }, $_[0] }
routine_wanting_callback( \&my_fetch_callback );
for my $datum ( @{ $returned_data } ) {
munge_it( $datum );
}
}
Update: Moved bracket after for so it would, you know, actually work. Duurr. Stupid trees making pollen affecting sinuses with their pollen making brane numbing congestion stuff.
Another example: You could also pass a coderef which stores the results by calling methods on an object you provide.
my $line_holder = Line::Holding->new( );
routine_wanting_callback( sub { $line_holder->hold( $_[0] ) } );
$line_holder->process_held_lines;
Nothing says the callback has to call a named subroutine sitting in the symbol table (unless the callback wanting routine says it takes the name of a subroutine of course; but that'd just be bad design :).
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|