Document possible assertion cases.

[ypiguet-epfl]

What about throwing exceptions instead of calling abort? See dashel/dashel-win32.cpp and dashel/dashel-posix.cpp

[stephanemagnenat]

If critical system resources necessary for the functioning of Dashel, such as the termination pipes, cannot be acquired, the program should quit. These will happen only in case of system severely over-loaded to the point of being totally dysfunctional.

Similarly, if there is a critical bug in the implementation of a system call, we should abort as we do not know the state of the system.

[ypiguet-epfl]

Then it should be clearly documented, so that potential users of the library can make an informed decision. There are applications where a communication error shouldn't be fatal.

[stephanemagnenat]

Yes I agree that this design choice should be documented. I thus relabel the issue as "enhancement" and change the title.