Databases
StackOverflow2013
Postsdbo
POUsing more than one special exception class
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing more than one special exception class
    primarykey
    data
    text
    <p>For the software we're developing at the company that I work for, we use a third-party library which is developed by a guy that we're constantly in contact with. His code is written in C++, and we use C# in the project.</p> <p>Normally, his library functions return error codes. I decided to have different exception classes to cover different ranges of error codes. For example, one exception class for parameter handling errors, one exception class for main operation errors, one exception class for input value errors and so on.</p> <p>He thinks it's not a good idea, and suggests using one exception class for the library that catches all the errors, and then fetches the error code from an XML file and outputs the problem to the user. He thinks, it's pointless to write more than one exception class. And also he says that he can't promise that the error codes will be the same in different versions of the library.</p> <p>I think it's a good idea to have more than one exception class because:</p> <ol> <li>There may be different situations that we need to handle the problem differently. Maybe when there's a parameter exception, do other stuff than just outputting an error. But he thinks his library is handling everything, and we should just stop the operation and output an error. I also can't think of many concrete examples of cases we need to handle differently, other than showing an error message. But I feel we may need it, and I'm afraid that I'm just violating the YAGNI principle.</li> <li>I think if he turns out wrong, and we need to handle things differently in different cases, I'll have to introduce conditional code (if error was A then do this, if B then do that). And it will be difficult to handle.</li> </ol> <p>I think it's a better idea to develop the program in a way that we can handle different types of exceptions differently. But then the guy has much more experience than me, plus he has much more credibility in the company (I'm a new intern) and I'm pretty new to software development and I feel like maybe he's right and I'm just trying to add extra code because it looks pretty, and violating the YAGNI principle.</p> <p>Do you think we should go with one class or more? And if you think we should use more than one exception class, what are your reasons?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. UShattenn
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUsing more than one special exception class
      1. This table or related slice is empty.
      1. VTUpMod
    1. COArgumentException, InvalidOperationException, ArithmeticException... these are all present in the .NET Framework - you only need to look at that to decide that there has to be some specifity in the error handling that you implement. Having error codes change meaning in different versions of a library is a nightmare. Working in software for a while has made me realise; it doesn't matter how much xp someone has, they can still be a bad developer or not really know what's best. Having said that, it depends exactly what your application is doing and whether recovering from an error is valid and OK
      singulars
      1. POUsing more than one special exception class
      1. USCharleh
    2. CO@Charleh well, if error codes are constantly changing meaning, it'd be just as difficult to use outside of .Net as well
      singulars
      1. POUsing more than one special exception class
      1. USEarlz
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload