cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Cocoon Wiki] Updated: ButterflyManifesto
Date Tue, 10 Aug 2004 11:07:37 GMT
   Date: 2004-08-10T04:07:35
   Editor: NiclasHedhman <>
   Wiki: Cocoon Wiki
   Page: ButterflyManifesto

   no comment

Change Log:

@@ -86,6 +86,8 @@
 Checked exceptions do more harm than good, so it would be wise to avoid them altogether.
Design instead a hierarchy of runtime exceptions and, whenever you need to catch an exception
thrown by a third party library, decide whether you can handle it locally. If you cannot,
wrap it in a runtime exception and throw the latter.
+Niclas Hedhman: If everyone follows this rule, then we don't know when there are exceptions
to catch, no situations you try to recover from, and we will have runtime unstable systems.
Sorry, I don't buy this argument for a second. Programmers need to do there job, not ignore
it for the 'time being' as lazy developers will definately do otherwise. Perhaps you can get
away with this in a request/response system like Cocoon, but a general recommendation that
nothing should throw checked Exception is foolish.
 == Code ==
 The Subversion repository for Butterfly is [

View raw message