Evaluate necessity of too large try-catch block - Githubissues

Feuermagier / autograder

Automatic grading of student's Java code

MIT License

13 stars 7 forks source link

Evaluate necessity of too large try-catch block #530

Open Luro02 opened 1 month ago

Luro02 commented 1 month ago

Description

This is a good indicator for code that could be improved, but not worth subtracting points for.

The following questions arise:

What should be done instead? Having duplicate catch blocks? Doesn't always make sense to have different error messages and duplicate code is bad
As a workaround one could move the code in the try block into a method and then it is fine? Where is the logic?