I have also discovered that the following syntax also works.
sub accept_out_cclose_after {
my $tkxfsr=shift;
my $afterid=shift;
my $delay=shift;
my $send_id;
if ($esub==1) { $send_id=Tkx::after( $delay , sub{&{$tkxfsr->{aft
+er}{$afterid}{sub}}()});}
elsif ($esub==2) { $send_id=Tkx::after( $delay , [$tkxfsr->{after}{$
+afterid}{sub}] );}
else { $send_id=Tkx::after( $delay , $tkxfsr->{aft
+er}{$afterid}{sub} ); }
$tkxfsr->{after}{$afterid}{eventid}=$send_id;
$tkxfsr->{after}{$afterid}{delay}=$delay;
}
perl huh-after.pl -esub 2
And i suspect that the [] notation in the Tkx::after call is doing the same thing i did with the sub {}, creating a one use anonymous subroutine reference.
-
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.
|