you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 1 day ago* (7 children)

No, it should not be an error. If you're making a calculator and your user enters 1/0, your program should not have the propensity to crash; the result should simply be NaN and you should choose how you display that result to your user.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 6 points 23 hours ago (4 children)

    You talk like error handling isn't a thing.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 22 hours ago* (3 children)

    fun fact: getting NaN from a numeric calculation is the error that you handle. if this wasn't obvious, please don't write code for anyone but yourself. hope this helps.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 7 points 19 hours ago

    if this wasn’t obvious,

    If this wasn't obvious, be glad of the chance to learn.

    If we all stopped as soon as something simple wasn't obvious, nobody would learn and nobody would do anything.

    What a terrible reply to someone. It cuts off curiosity and says "You are too stupid to do anything."

    Yet I bet there was a time that even with that very specific thing, you didn't think of it that way.

  • source
  • parent
  • [–] 4 points 19 hours ago (1 child)
  • [–] 1 point 16 hours ago

    fault v. error v. failure

    In common language they can be synonyms, but often aren't in places (like computing) where there's a useful difference. A page fault isn't an error; a handled error doesn't result in a failure; fault-tolerant systems fail less often than their components fault.

  • source
  • parent