adamsj

They laughed at Joan of Arc, but she went right ahead and built it. --Gracie Allen

How about nothing?

given ($foo) {
  when (1) {print "One";};
  when (2) {print "Two";};
  print "Didn't fit any case we know about";
}
[download]

Indent to taste.

UPDATE
I don't think that "normal code" will often see a difference. While I can dream up situations where I think it matters, in all of them you are doing evil, awful things that you probably shouldn't. (Like using a default to shortcircuit out of a function.)

That is already defined to work but doesn't solve the problem of the presense of a real "default" block changing the handling of exceptions.

        - tye (but my friends call me "Tye")

If anyone has a brilliant idea for a shorter keyword than default, I hope they'll send it in.

Not shorter, but I think it's easier to read and a lot better:

given $foo {
 when 1 { ... }
 when 2 { ... }
 when we have tried all other options and
      really have nothing left but this last resort { ... }
}
[download]



:)

2;0 juerd@ouranos:~$ perl -e'undef christmas'
Segmentation fault
2;139 juerd@ouranos:~$
[download]

I pondered that for a bit but the best I could to was orelse. But that's even worse. :(.

Hmmm ...

given EXPR {
      otherwise { ... }
}

given EXPR {
      default { ... }
}
[download]

default definitely looks better here. I wonder how often people write empty switch statements though? Then again, given isn't your father's switch so past coding patterns may very well not apply.

given EXPR 
{
     when EXPR { }
     when EXPR { }
     ...
     japh {      }
}
[download]

metadoktor

"The doktor is in."

You are missing a colon.

given EXPR 
{
     when EXPR { }
     when EXPR { }
     ...
     japh: {      }
}
[download]

Happy to help,
Ben

:-)