Read-only is a designation for any object or construct which can no longer be altered after creation, it can only be read. This can refer to both hardware and software constructs such as read-only memory chips like BIOS and CMOS and CD/DVD/Blu-ray-ROMs for hardware, and read-only files for software constructs. In either case the contents of the...
Exception handling is a mechanism in which a programming construct is used to consistently trap, intercept and handle the error occurred during application execution. The Common Language Runtime (CLR) of .NET Framework is designed to use an exception handling model based on exception objects and protected blocks of code.
The features of exception handling mechanism implemented in CLR are as follows:
a) Each language can have its own specification for handling exceptions without any restrictions
b) Exceptions are generated and handled irrespective of the language used and type of code (managed or unmanaged)
c) Exceptions can be thrown across process or machine boundaries
.NET runtime throws exceptions as objects derived from System.Exception class that contain error details, including message and line of code where the error occurred, etc. The construct "try..catch..finally" is used for exception handling. While "try" (where exceptions are anticipated) and “catch” (where exceptions are handled) blocks are mandatory, the "finally" (where code executed in any case) block is optional.
When compared to error handling implemented using traditional methods - like usage of return code as in Component Object Model (COM) and "go to" statements, as in Visual Basic, etc. - the main benefits of exceptions in .NET are trapping of all failures, elimination of process of checking return value and its usage (if invalid) in applications, usage in scenarios where there is no return value such as constructors, increased reliability and better performance.
While Java provides "checked" exceptions that help in preventing incidence of unhandled exceptions during compilation, they cannot be used for errors which are unrecoverable failure. Exception handling in C++ differs from that in .NET by not having the "finally" block for cleaning up resources and without any restriction for the type of exception.
Read More »
Join 138,000+ IT pros on our weekly newsletter
Home | Advertising Info | Write for Us | About | Contact Us
2010 - 2014
Janalta Interactive Sites: