Comments on: A guidance to Exception Handling http://www.rvramesh.com/2010/05/a-guidance-to-exception-handling/ - Simplicity by design Sun, 06 Feb 2011 07:42:56 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: rvramesh http://www.rvramesh.com/2010/05/a-guidance-to-exception-handling/comment-page-1/#comment-78 rvramesh Thu, 06 May 2010 06:41:54 +0000 http://www.rvramesh.com/?p=76#comment-78 Well, my view on logging for a framework and library is that, they should log, for tracing but should not suppress exceptions. Preferably they should use IoC for logging so that applications can configure what should be used for logging. Well, my view on logging for a framework and library is that, they should log, for tracing but should not suppress exceptions. Preferably they should use IoC for logging so that applications can configure what should be used for logging.

]]> By: Sherwin James http://www.rvramesh.com/2010/05/a-guidance-to-exception-handling/comment-page-1/#comment-77 Sherwin James Tue, 04 May 2010 18:31:04 +0000 http://www.rvramesh.com/?p=76#comment-77 Pretty good points/guidance raised, I agree with pretty much all of these. Some items may require a little more explanation as to why (e.g. #6).<br><br>I wonder if the guidance changes a bit when building libraries (as opposed to applications)? Should libraries log anything? Pretty good points/guidance raised, I agree with pretty much all of these. Some items may require a little more explanation as to why (e.g. #6).

I wonder if the guidance changes a bit when building libraries (as opposed to applications)? Should libraries log anything?

]]>