Re: Re: Perl::TK - fileevent and script execution theory

[crabbdean]

in reply to Re: Perl::TK - fileevent and script execution theory
in thread Perl::TK - fileevent and script execution theory

I've noticed in the above code that instead of exiting at the eof(CHILD) section it exists at the bottom "else" statement. All exiting commands I'm wanting to execute such as cleanup or "destroys" I'm putting here, which seems illogical. I would have thought it would exit at the "eof". Is there a reason for this?

Update: It would seem more correct to put the whole bottom "sysread" if statement as and "else" to the "eof". See below.

    if (eof($handle)) {
        $widget->fileevent($handle, "readable", undef); # cancel bindi
+ng
        return ;
    } else {
        if (sysread ($handle, $_, 128)) {
            $tx->insert('end', $_); # Append the data read
            $tx->yview('end');
        } else {
            $tx->insert('end', times);
            $tx->yview('end');
            $widget->fileevent($handle, "readable", undef); # cancel b
+inding
            return;
        }
    }