Loading ...
Sorry, an error occurred while loading the content.

158209[XP] Re: Pattern Encoded Suffix

Expand Messages
  • MarvinToll.com
    Sep 23, 2012
    • 0 Attachment

      Thanks for your feedback.

      The notion that a a Java author precisely considers whether they are using one of the two exception mechanisms to indicate a true unanticipated exceptional break-down, or as an indication of alternate path processing (e.g. instead of return codes), is the thought-path I'm suggesting for consideration.

      As you mentioned (twice), there are contexts where the author could be wrong... and the code catching can respond as required.

      Said another way, I'm suggesting that authors throwing exceptions clarify the intended usage... even though a client's corner-case might warrant a different course than the author anticipated.


      --- In extremeprogramming@yahoogroups.com, "JeffGrigg" <jeffreytoddgrigg@...> wrote:
      > The code that throws an exception should not (and cannot reasonably) know how the code that catches it will handle it. It's the responsibility of the code that catches the exception to do the right thing.
    • Show all 191 messages in this topic