JaroslavTulach at 08:54, 16 June 2016 - 2016-06-16 08:54:51

←Older revision Revision as of 08:54, 16 June 2016
Line 1: Line 1:
-
[[Java]] made [[checked exception]]s popular topic of many debates. When designing a [[Java]] one is often confronted with the necessary choice between [[checked exception]]s or runtime [[exception]]s. There are two camps who prefer the opposite solutions, with an attempt to bring some of rationality (and less [[cluelessness]]) into the discussion [[I]] have come up with a few [[:APIDesignPatterns:Exceptions|Exceptional API Design Patterns]].
+
[[Java]] made [[checked exception]]s popular topic of many debates. When designing a [[Java]] one is often confronted with the necessary choice between [[checked exception]]s or runtime [[exception]]s. There are two camps who prefer the opposite solutions, with an attempt to bring some of rationality (and less [[cluelessness]]) into the discussion [[I]] have come up with a few [[:APIDesignPatterns:Exceptions|Exceptional API Design Patterns]] and organized them into [[:Category:APIDesignPatterns:Exceptions]] category.
 +
 
 +
[[Category:APIDesignPatterns:Exceptions]]

JaroslavTulach: New page: Java made checked exceptions popular topic of many debates. When designing a Java one is often confronted with the necessary choice between checked exceptions or runtime [[... - 2016-06-16 08:53:07

New page: Java made checked exceptions popular topic of many debates. When designing a Java one is often confronted with the necessary choice between checked exceptions or runtime [[...

New page

[[Java]] made [[checked exception]]s popular topic of many debates. When designing a [[Java]] one is often confronted with the necessary choice between [[checked exception]]s or runtime [[exception]]s. There are two camps who prefer the opposite solutions, with an attempt to bring some of rationality (and less [[cluelessness]]) into the discussion [[I]] have come up with a few [[:APIDesignPatterns:Exceptions|Exceptional API Design Patterns]].