ASPP/pelita — pull request #162 by Debilski (2012-08-19 17:40:08+00:00)
Title: Feature/catch client exceptions

There may be some need to discuss this commit:

The first two commits introduce a mechanism to print a short info line before the stack trace, when an exception is raised by client code (in a remote game). I think this is a good idea as it tells the user more clearly which Team was involved.
The client code will then immediately exit after this exception and the player will lose.

The third commit introduces a deviation from this: Here every exception prints a stack trace but is otherwise ignored (sending back an invalid move to SimpleServer which is internally handled in the same way as a timeout). This may be a good thing as even our own hand-written Players sometimes create exceptions under rare circumstances (q.v. issue #158) and it may be to strict to end the game immediately.

On the other hand, there may be cases where an immediate return may be appropriate. One is the `ExitLoop` exception which is used internally – but there may be other exceptions as well where it might be better to exit directly.

What do you think?