in reply to Re: Interaction of Windows Batch files and Perl's system() function
in thread Interaction of Windows Batch files and Perl's system() function

This means that the example using Ruby probably works because Ruby itself (by design) catches the interrupt before spawning a sub-process?

Thank you for your suggestions and your elaborate explanation. Actually, in my application it indeed makes sense to catch SIGINT in my Perl program, so this is what I will do.

-- 
Ronald Fischer <ynnor@mm.st>
  • Comment on Re^2: Interaction of Windows Batch files and Perl's system() function
  • Download Code

Replies are listed 'Best First'.
Re^3: Interaction of Windows Batch files and Perl's system() function
by BrowserUk (Patriarch) on Sep 07, 2011 at 13:16 UTC
    This means that the example using Ruby probably works because Ruby itself (by design) catches the interrupt before spawning a sub-process?

    Hm. The first thing is that Windows doesn't do signals. perl.exe simulates POSIX-style signal handling to some extent.

    ^C generates a "Console Event". How this is processed by related processes depends in large part by whether the processes share a console or not; and b) whether they are formally related into a process group or not.

    For more of the gory details see the discussion about CREATE_NEW_PROCESS_GROUP in the Process Creation Flags passed to the CreateProcess() function. See also the related discussion for GenerateConsoleCtrlEvent Function.

    There are several ways that Ruby might achieve it's behaviour. Without reading the source it isn't possible to know which is used.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom