© 2015-2017 John Abbott
GNU Free Documentation License, Version 1.2

CoCoALib Documentation Index


User documentation

CoCoALib offers a simple mechanism for "handling signals" (i.e. detecting and reacting to interrupt signals such as "control-C" on Linux). If you do not know anything about "interprocess signals", you can safely skip this manual entry.

Since CoCoALib is a software library, it does not change any existing signal handlers unless you tell to do so explicitly.

There are two parts to the signal handling mechanism in CoCoALib:

Normally it makes sense to call CheckForInterrupt only inside loops which may take a long time to complete. Unless you want the program to exit when a signal is detected, you must somewhere catch any CoCoA::InterruptedBySignal object thrown by CheckForInterrupt and then handle it as you want.

Constructors and pseudo-constructors

There is just one class, InterruptReceived (which is derived from the CoCoALib class exception). It serves as a base class for the exceptions potentially thrown by a call to CheckForInterrupt.


CheckForInterrupt first checks whether a signal has arrived; if so, it throws an exception of type InterruptedBySignal. If no signal has arrived, it then checks whether timeout has occurred; if so, an exception of type InterruptedByTimeout is thrown.

Maintainer documentation

The implementation is quite simple.

Being a library CoCoALib sets no signal handlers unless explicitly told to do so, and for "cleanliness" the handlers are set and reset (to the previous value) using scoped "RAII objects" (called SignalWatchers).

The function CheckForInterrupt is very simple, and should be quick when no signal has been detected. It is not inline because I do not think it needs to be.

The InterruptReceived is derived from CoCoA::exception; the exception subobject contains the message "External interrupt", and the context string (which was given to the call to CheckForInterrupt, and which should indicate the location of that call).

Bugs, shortcomings and other ideas

I've no idea what happens in multithreaded execution.

Main changes