Re: Probably an easy one - store command in variable.

The simple (and wrong) answer is, of course, eval.

Any variable declared within and eval(STRING) will go out of scope at the end of the eval().

Perhaps you should take a step back and say why you think that you want to do this.

I suspect the thing you are really looking for is the anonymous subroutine.

Comment on Re: Probably an easy one - store command in variable.

Replies are listed 'Best First'.
Re^2: Probably an easy one - store command in variable. by Joost (Canon) on Sep 15, 2005 at 17:08 UTC
expanding on the anonymous subroutine: you'd need something similar to this: `my @list = qw(some random values); my $text = "bla bla bla"; my $command = sub { $d->checklist( text => $text, list => \@list ); }; my @returnlist = $command->();` [download] In this example $command is a closure - it "captures" the $text and @list variables. Depending on your problem that might or might not be the most elegant solution - without any context, it looks like you could also make a "normal" subroutine and pass those variables to it. YMMV. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: Probably an easy one - store command in variable.
by Joost (Canon) on Sep 15, 2005 at 17:08 UTC

my @list = qw(some random values);
my $text = "bla bla bla";
my $command = sub {
   $d->checklist( text => $text, list => \@list );
};
my @returnlist = $command->();
[download]

"What should it profit a man, if he should win a flame war, yet lose his cool?"

[reply]
[d/l]