I cannot really recommend this approach.

If a second INT signal is received, zap will be called again. Since the housekeeping involves opening and writing to files things will start to go a little bezerk, since you will have two (or more) paths of execution running asynchronously. If files are being appended to, the results will be disastrous. Try running the following code:

#! /usr/bin/perl -w use strict; my @a = (1..200000); $SIG{INT} = sub { open OUT, '>>logfile'; foreach( @a ) { print OUT "$_\n"; } close OUT; exit; }; 1 while 1;

If you feed this an INT signal, followed by another one in less than the time it takes to write out the file you will some very interesting results in the logfile...

--
g r i n d e r

In reply to Re:x2 keyboard input during runtime... by grinder
in thread keyboard input during runtime... by Shadowfax

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.