Handle unspecified Exception

[Tjalling-dejong]

In many places in the code there Try - Except clauses that use an unspecified Exception. This excepts any error and can cause unexpected results. Bugs can go unnoticed.

It is best practice to only handle errors that you specify in the code. If an unexpected error pops up to the code should fail instead of pass.

[kdberends]

"It is best practice to only handle errors that you specify in the code. If an unexpected error pops up to the code should fail instead of pass."

I disagree. Exceptions are usually caused by some error in the input files. If we let the program fail after each exception, the user has no idea how many errors are in the files. Debugging would take a long time.

Ideally, the code should continue running, but report all exceptions to the user. fm2prof outputs a report to the user specifying the number of errors, and errors are color-coded in the fm2prof output. Bugs should not go unnoticed, but also not crash the program.