See perlipc for ways to trap CTRL-C.

Quote from the Camel book: END blocks are skipped only if you exec or your process is blown away by an uncaught catastrophic error.

I guess you could call CTRL-C a catastrophic error, although I would go a bit easier on the words for such a common visitor... :)

But to be serious, END and DESTROY blocks for instance, are skipped when you press CTRL-C. I think it is called the signal INT and it is a "fatal" signal for your program, so it promptly exits right away, no matter what it was doing, and without cashing in the $200.

Hope that helps.

---

You have moved into a dark place.
It is pitch black. You are likely to be eaten by a grue.