Support for easy SIGINT handler

[WebFreak001]

so Ctrl-C doesn't close the application, but usually they are weird to write using the C apis

[Dechcaudron]

just wondering, why shouldn't Ctrl-C close the application?

[WebFreak001]

if you want to do cleanup, stopping servers, when autocompleting simply remove what was typed, etc

[Dechcaudron]

ok, so Ctrl-C should be able to gracefully stop the app. Is that what you mean?

[WebFreak001]

I want something like

handleInterrupt(() {
  writeln("no");
});

[Dechcaudron]

I'll see how I go about it. I've never worked with OS signals before and don't know the apis. Still, handling the Ctrl-C signal should not digest it. The application should exit gracefully, but exit regardless.

[WebFreak001]

see nodejs shell, it doesn't exit on first ctrl-c either, only clears the input first and exits on the second one

[Dechcaudron]

yeah, I've come across a couple apps that do that as well. This is definitely useful, but I need to come up with a good API. Goes to my TODO.

[Dechcaudron]

Okay, so I've been doing some research about this. Off the top of my head, I'd say the way to go is to create a separate library which takes care of handling IPC signals in POSIX systems, since not only apps that use cli may benefit from custom signal handling. The approach is exactly the same to handle SIGINT or virtually any other signal, so that'd make it more flexible as well. What do you think?