I was looking for ways to pass out-of-band parameters to the loop subroutines (preferably without requiring the users to make messy changes), and this idea of using named parameters in combination with a splatted list occurred to me.
#!/usr/bin/pugs
use v6;
#use Test;
#plan 2;
sub oob(+$x = $CALLER::_, *@lst) {
return ($x,@lst);
}
sub runner() {
$_ = "qqq";
oob("a","b","c");
}
my ($x, @lst) = runner();
say "x = *$x* lst = *",~@lst,"*";
#is($x, 'qqq', '... default named parameter with $CALLER_ and a list',
+ :todo<bug>);
#is(~@lst, 'a b c', '... list after default named parameter with $CALL
+ER_', :todo<bug>);
What I actually got was:
x = *a* lst = *b c*
and not:
x = *qqq* lst = *a b c*
This was unexpected after seeing examples in E06, so it could be a bug test (with the Test stuff uncommented). Or I may be completely misunderstanding positional parameters.
-
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.