== Briscola.expected_event implementation is troublesome ==
The current(not completely working) implementation of expected_event is a big mess. The method is too long, has long lines and it's ugly. This is due to the different possibilities in which events may occur.
All this could be solved using an "event graph", in which each node represents an event and has the possible following events as children. In this way it should be easier to keep track of the valid events.
Also this may help when we'll try to automate the game creation/validation.