Brilliant exception handling I found in an app i had to work on

  • ipkpjersi@lemmy.one
    7·
    1 年前

    Actually, exception rethrowing is a real thing - at least in Java. You may not always want to handle the exception at the absolute lowest level, so sometimes you will instead “bubble” the exception up the callstack. This in turn can help with centralizing exception handling, separation of concerns, and making your application more modular.

    It seems counter-intuitive but it’s actually legit, again at least in Java. lol

    • TwilightKiddy@programming.dev
      1·
      1 年前

      Rethrowing caught exception in C# is just throw;, not throw ex;. This will delete old stack trace, which is very punishable if someone debugs your code later and you’re still around.

        • TwilightKiddy@programming.dev
          1·
          1 年前

          throw ex; treats ex as a new exception, so, it starts a new stack trace for it from itself and deletes stack trace that was saved in ex.StackTrace. On the other hand, throw; takes already present exception in the scope and throws it without modifying the stack trace, preserving the original method that threw ex in the stack trace.

          I feel like I wrote the same thing twice. I’m a bit bad with explaining stuff, feel free to ask more specific questions if you still don’t understand the difference.

    • chillhelm@lemmy.world
      5·
      1 年前

      Depending on the language it either does nothing and just adds code bloat or (and this would be much worse) it will catch any exception that can be implicitly cast to type Exception and throw it as type Exception. So the next higher scope would not be able to catch e.g. a RuntimeException or w.e. to handle appropriately. It could only catch a regular Exception even if the original error was a more detailed type.

      • StudioLE@programming.dev
        1·
        1 年前

        It’s C# so it’s just rethrowing the original exception.

        It might also be messing with the stack trace though which can be a bit frustrating for future debugging. But that’s only a vague recollection of something I read in the past so I could be wrong

        • Pieisawesome@lemmy.world
          1·
          1 年前

          Throwing exceptions are very costly due to the stack trace, so building the stack trace twice will cause a big performance hit

          • TwilightKiddy@programming.devEnglish
            1·
            1 年前

            Correct me if I’m wrong, but this will actually cut the stack trace and then start another one from your try-catch block, which is an evil thing to do towards those who will actually read your stack traces. To preserve the stack trace you do throw;, not throw ex;, and I’m assuming IDE is underlining that statement exactly for this reason.

    • grimmi@feddit.de
      2·
      1 年前

      If this is C# (and it looks like it is), this leads to you losing the original stack trace up until this point.

      The correct way to do this in C# is to just throw; after you’re done with whatever you wanted to do in the catch.

      • jyte@lemmy.world
        1·
        1 年前

        wait what ?

        So you are saying that the following code will keep throwing e but if I used throw e; it would basically be the same except for the stack trace that would be missing the important root cause ?!

        try {
} catch (WhateverException e) {
    // stuff, or nothing, or whatever
    throw; 
}
        • TwilightKiddy@programming.dev
          1·
          1 年前

          Exactly. Aside from deleting your already built stack trace, as a bonus you’ll get another stack trace building call, enjoy wasted CPU cycles.

    • js10@reddthat.com
      1·
      1 年前

      Then the parent function would catch the original exception if it was never caught in the first place. All this does is bork the stacktrace.

    • Jaloopa@beehaw.org
      3·
      1 年前

      Why wouldn’t it? It’s syntactically valid C#, with the added bonus of destroying the stack trace