On Wed, Dec 3, 2008 at 2:26 PM, Mark J. Reed <[EMAIL PROTECTED]> wrote:
> Overall, the goal is to ensure that by the end of the loop the program is in
> the state of having just
> called doSomething(), whether the loop runs or not - while also ensuring that
> the program is in that
> state at the top of each loop iteration.
... including the first, just to point out the problem.
We can guarantee it's set at the top of each loop iteration with
ENTER, but that doesn't get run if the loop never runs.
We can guarantee it's set at the end of the loop with LAST, but that
also doesn't get run if the loop never runs, and doesn't take care of
the first iteration.
> It does seem like a closure trait sort of thing, but I don't think
> it's currently provided by the p6 spec.
I think the cleanest solution is the "coy" one. This works in pugs:
do
{
doSomething();
if (someCondition())
{
doSomethingElse();
redo;
}
}
But I'm not sure that redo in a do block is supposed to be allowed.
If not, you have to do something like this:
loop
{
doSomething();
if (someCondition())
{
doSomethingElse();
}
else
{
last;
}
}
--
Mark J. Reed <[EMAIL PROTECTED]>
