Relative Content

Tag Archive for exception-handling

Generic way of handling exceptions in windows phone? [closed]

It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 12 years ago. I mean what are some of the ways […]

Exception Handling Frequency/Log Detail

I am working on a fairly complex .NET application that interacts with another application. Many single-line statements are possible culprits for throwing an Exception and there is often nothing I can do to check the state before executing them to prevent these Exceptions.

Central Exception Handler

Recently I’ve been thinking about a general ExceptionHandler, that I could initialize once in my app context and inject it everywhere. The idea that it will have quite simple interface with just public void handle(Exception ex), and then according to exception type it should decide what to do, maybe just log it, or show an alert message to the user, or maybe kill the whole app.

Decision for Unchecked Exceptions in Scala

As a java programmer, I have always been critical of Unchecked Exceptions. Mostly programmers use it as an en-route to coding easiness only to create trouble later. Also the programs (though untidy) with checked exceptions are much robust compared to unchecked counterparts.

Best way to throw exception and avoid code duplication

I am currently writing code and want to make sure all the params that get passed to a function/method are valid. Since I am writing in PHP I don’t have access to all the facilities of other languages like C, C++ or Java to check for parameters values and types

Reporting and handling asynchronous process errors to a client

I have a product with two separate applications. The core of the product lives in the database (oracle) and runs according to a schedule. The other is a client application (currently ASP.NET MVC3) used to manage the database application. There are three levels of validation going on; client, server-side, and database before the client data is saved to the database.

Why would I use Control.Exception in Haskell?

I’m trying to really master Haskell error handling, and I’ve gotten to the point where I don’t understand why I would use Control.Exception instead of Control.Monad.Error.