Frysk exceptions

[Sami Wagiaalla <swagiaal@redhat.com>]

I have been meaning to write this for a while to clarify to my self the 
frysk strategy with respect to Exceptions and handling.

These are my practices; please tell me if you agree or disagree:

  * All frysk exceptions are (should ?) be unchecked exceptions ie 
extend RunTimeException.
  * Exceptions should never ever be ignored.
  * Exceptions can be ignored (handled) if they are specific enough (eg 
operation XYZFailedException)
  * Except for certain cases catch statements should be as specific as 
possible.
     So no catch(Exception e) statements, but 
catch(SymboleNotFoundException e).
  * Exceptions are better than returning null.

All other exceptions -which are not caught-, should be printed out in 
the most obvious way possible. This tells the use that there is a bug in 
frysk and that they should report it. The alternative (if it was logged, 
or cleaned up) is that the user assumes it is a non fatal error and 
continues to use frysk only to find it in a bad state much later. 
Resulting a difficult problem to debug.