From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Wed, 28 May 2008 23:14:06 -0500
On Wed, May 28, 2008 at 10:05:32PM -0400, Bob Rogers wrote:
> Pos? Named? Reqd? => Example
> yes no yes => .param pmc A
> yes no no=> .param pmc B :optional
> y
Patrick R. Michaud wrote:
Since there's a fair amount of existing code that may be doing
slurpy positionals before named parameters, I propose, perhaps
as an interim step, that we say that positional slurpy array
parameters must come after all positional and lookahead parameters
(but could come
On Wed, May 28, 2008 at 10:05:32PM -0400, Bob Rogers wrote:
>From: Allison Randal <[EMAIL PROTECTED]>
> >
> > Any of these alternatives can be marked as optional. Positional
> > parameters must come before all lookahead or named parameters. Lookahead
> > parameters must come before all nam
From: Allison Randal <[EMAIL PROTECTED]>
Date: Thu, 29 May 2008 02:22:37 +0200
. . .
Any of these alternatives can be marked as optional. Positional
parameters must come before all lookahead or named parameters. Lookahead
parameters must come before all named parameters. Posit
(After talking about it on the phone today.) From the Parrot side, we
have basically 3 binary factors: named (or not), positional (or not),
and optional/required.
The unmarked case is a required parameter that can be passed as a
positional argument and can't be passed as a named argument. (Per
