Error handling

[ddelventhal]

Currently we use many different methods of error handling:

1. CorsikaIOException
2. enum Status
3. INFO, ERROR, FATAL

The main question for designing a error handling API is whether we need to recover from and error.
If we need to recover, we should probably use CorsikaIOException and use try{} as needed.
Otherwise we could just use an assert-like method that prints a message and aborts on error.

[javierggt]

The functions that return enum Status are not for "errors," they are for things that are expected and it delays the decision on whether it is an error to client code. Failure reading a file should not be an error (or depends on the circumstances). Throwing an exception in cases like this is also not a good idea, I think. We do not want to use exceptions to control the flow of a program.

I will look into this.