Re: RFC: add a mechanism to call epicsExit when signals are received

[Ralph Lange via Tech-talk <tech-talk at aps.anl.gov>]

Another attempt to summarize...

1. You want EPICS Base to provide - on demand, after calling a function - an extra thread that waits on a specific exitEvent and calls epicsExit when it receives it.

I'm generally fine with that, given that this is portable, lightweight, and doesn't add anything if you don't call the function.

To not expose the event mechanism, I would add another function wrapping around sending exitEvent.

2. You want EPICS Base to install signal handlers for an arbitrary number of signals, which send the exitEvent when they get called.

For me, this is the more problematic part. Not portable, possible side effects.

Could Base implement the first part (exit-on-event), and the second part (signal handlers) be left to a separate module? Such a module could provide implementations for Windows and Linux and be a lot more flexible, with a lifecycle that is not bound to EPICS Base. 

Cheers,

~Ralph