From @jkeenan

The New York City Rakudo Star study group is working its way through
the Using Perl PDF from Rakudo's github site. Working through the
examples in Chapter 4, Subs and Signatures, we believe we have
identified a case where the code example does not work​:

At bottom of page 34, we see​:

sub design-ice-cream-mixture(​:$name!, $base = 'Vanilla') {
  say "Creating a new recipe named $name!";
  }

design-ice-cream-mixture(name => 'Plain');

FAILS with​:

===SORRY!===
Can't put required parameter after variadic parameters at line 3,
near ") {\n sa"

However, if we but 'base' before 'name' in the signature, it works​:

sub design-ice-cream-mixture($base = 'Vanilla', :$name!) {
  say "Creating a new recipe named $name!";
  }

design-ice-cream-mixture(name => 'Plain');

This works.

Can anyone confirm that it is merely the code exammple on page 34
which is incorrect?

Thank you very much.

kid51

From @masak

On Sat Aug 14 11​:33​:18 2010, jkeen@​verizon.net wrote​:

The New York City Rakudo Star study group is working its way through
the Using Perl PDF from Rakudo's github site. Working through the
examples in Chapter 4, Subs and Signatures, we believe we have
identified a case where the code example does not work​:

At bottom of page 34, we see​:

sub design-ice-cream-mixture(​:$name!, $base = 'Vanilla') {
say "Creating a new recipe named $name!";
}

design-ice-cream-mixture(name => 'Plain');

FAILS with​:

===SORRY!===
Can't put required parameter after variadic parameters at line 3,
near ") {\n sa"

However, if we but 'base' before 'name' in the signature, it works​:

sub design-ice-cream-mixture($base = 'Vanilla', :$name!) {
say "Creating a new recipe named $name!";
}

design-ice-cream-mixture(name => 'Plain');

This works.

Can anyone confirm that it is merely the code exammple on page 34
which is incorrect?

Confirmed​: the error message is wrong, but it's right in that one cannot put this kind of thing
after that kind of thing​: namely, one cannot put a named parameter after a positional one in a
signature.

The RT System itself - Status changed from 'new' to 'open'

From @moritz

Thanks for the report, I've now fixed the example in the book.

@moritz - Status changed from 'open' to 'resolved'