I'm just use ing the CQLogin module in script A, so in this case I cannot use kill as there is no separate PID for script B, is that correct?
Yes, that is correct. In the situation you have described there is no child script.
Suggestion 1:
Set interrupt to die, then use eval to trap the die in the code. This modification could be in either the primary module or the CQLogin module, depending on if you want to change the calling contract of the CQLogin.
Suggestion 2:
Use a parsing module that has already anticipated and fixed these issues.
#!/usr/bin/perl
use strict;
use warnings;
my $INTERRUPT_MESSAGE = "caught sig int user interrupt";
$SIG{'INT'} = sub { die $INTERRUPT_MESSAGE };
my $login = new CQLogin();
my $username = eval { $login->autoLogon() };
if ( !defined $username && $@ ) {
print STDERR "wow, we got a signal\n\n"; #just for demo purpose
die $@ unless $@ eq $INTERRUPT_MESSAGE;
}
print "Success, our username is [$username]\n\n";
#note, username will be undef if the user interrupted.
package CQLogin;
sub new
{
my $class = shift;
return bless {}, $class;
}
sub autoLogon
{
my $self = shift;
chomp( my $username = <STDIN> );
return $username;
}
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|