Okay, so signals don't work ActiveState builds.
Does anyone out there have a trick or spoof for catching ctrl-c?
I've tried running nested eval's, double processes . . .
I am racking my brain for a way to get around the limitation and make sure
some processing is done after everything is blown away.
For me, the real point is that I have some clean up that HAS TO BE DONE . .
. I don't care about the ctrl-c per se . . . I just want to make sure my
clean up is done even if the user blows me away.
Any ideas for a work around?
Frank
---
You are currently subscribed to perl-win32-users as: [archive@jab.org]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
