• JustANoone@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      16
      ·
      edit-2
      1 year ago

      This is a reucurring theme at this specific subject unfortunately. He doesn’t seem to put much effort into it, as most slides are just plain text and nothing else. I stopped attending after the second class.

      • DrownedAxolotl
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        1
        ·
        1 year ago

        That truly sucks. Yeah, some professors can be like that. I had a math professor offer bonus points to the first 3 students completed the assignment, only for the majority to cheat and just look up the answer and turn that in. It became a contest of who could copy the fastest and one student even admitted to doing it, but she just didn’t care and gave points to the cheaters anyway.

    • MasterBlaster@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Thanks for looking that up, because the application exception is the way I originally learned this myself. And I’ve been doing .net for 20 years.

      • JustANoone@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Do you guys still use it in practice though? I have never seen or heard about this until now.

        • MasterBlaster@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          I don’t create many exceptions in c#. The way I handle errors doesn’t require it for (damn near) everything. Java makes throwing named errors more important, and consequently I wrote more for Java.

    • JustANoone@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      1 year ago

      I should have elaborated, but basically what MD87 replied. During the development of .NET it was decided that every exception caused by programs should inherit from ApplicationException, and all system errors should inherit from SystemException. Unfortunately .NET devs didn’t follow this and now everything should just inherit Exception since it’s easier to check. Interestingly, both SystemException and ApplicationException seem functionally identical to Exception.

      • Greg@feddit.de
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        Which actually makes sense. Java logic with exceptions that you cannot catch is a practice no other language has.

  • Scrubbles@poptalk.scrubbles.tech
    link
    fedilink
    English
    arrow-up
    10
    ·
    1 year ago

    I have never extended from or caught an application extension in my entire career. Agree with Microsoft, if it’s an application exception it’s coming from the framework. All of mine derive from exception.