© 2017 John Abbott, Anna M. Bigatti
GNU Free Documentation License, Version 1.2

CoCoALib Documentation Index


User documentation

A SignalWatcher is part of the CoCoA mechanism for detecting and reacting to interprocess signals (sometimes known as "interrupts").

Since CoCoALib is a software library, it does not change any existing signal handlers unless you tell to do so explicitly. A SignalWatcher is an RAII object: creating it installs CoCoA's "signal handler" for the given signal; destroying it, reinstates the previous "signal handler".

A SignalWatcher by itself does not do much: it simply "takes note" when a signal of the given type arrives. CoCoALib can react to a signal only after it has been noted by a SignalWatcher and the procedure CheckForInterrupt is called -- see interrupt for a summary, or look at the example programs.

If several signals arrive before CheckForInterrupt is called, only the last signal is heeded; the others are "forgotten".

Constructors and pseudo-constructors

The exception which thrown when CheckForInterrupt detects a signal is created by the following constructor:


Let SW be a SignalWatcher.


Let SW be of type SignalWatcher; and let INTR be of type InterruptedBySignal

Maintainer documentation

The implementation is straightforward (except for SetSignalReceived which still involves a "dodgy hack" from an earlier implementation).

For portability the CoCoALib signal handler just sets a "hidden" global variable CoCoA::<anon>::SignalReceived (of type std::sig_atomic_t).

The CoCoALib signal handler is registered by creating an object of type SignalWatcher; its constructor takes as arg the signal to detect. The original signal is restored when the SignalWatcher is destroyed (or when the mem fn myDeactivate is called).

Bugs, shortcomings and other ideas

I do not know how threadsafe the implementation is: hopefully it is good, but I doubt it is perfect.

Main changes