For more information, see the Exceptions versus assertions section. Use exceptions when the code that handles the error is separated from the code that detects the error by one or more intervening function calls.
Consider whether to use error codes instead in performance-critical loops, when code that handles the error is tightly coupled to the code that detects it. For every function that might throw or propagate an exception, provide one of the three exception guarantees: the strong guarantee, the basic guarantee, or the nothrow noexcept guarantee.
For more information, see the Exception specifications and noexcept section. Use standard library exception types when they apply. Derive custom exception types from the exception Class hierarchy. The exception mechanism has a minimal performance cost if no exception is thrown. If an exception is thrown, the cost of the stack traversal and unwinding is roughly comparable to the cost of a function call.
Additional data structures are required to track the call stack after a try block is entered, and additional instructions are required to unwind the stack if an exception is thrown.
However, in most scenarios, the cost in performance and memory footprint isn't significant. The adverse effect of exceptions on performance is likely to be significant only on memory-constrained systems. Or, in performance-critical loops, where an error is likely to occur regularly and there's tight coupling between the code to handle it and the code that reports it. In any case, it's impossible to know the actual cost of exceptions without profiling and measuring.
Even in those rare cases when the cost is significant, you can weigh it against the increased correctness, easier maintainability, and other advantages that are provided by a well-designed exception policy.
Exceptions and asserts are two distinct mechanisms for detecting run-time errors in a program. Use assert statements to test for conditions during development that should never be true if all your code is correct.
There's no point in handling such an error by using an exception, because the error indicates that something in the code has to be fixed. It doesn't represent a condition that the program has to recover from at run time. An assert stops execution at the statement so that you can inspect the program state in the debugger. An exception continues execution from the first appropriate catch handler.
If the caller chooses not to catch them, then the exceptions are handled by caller of the caller. We can create a hierarchy of exception objects, group exceptions in namespaces or classes, categorize them according to types. The throw keyword throws an exception when a problem is detected, which lets us create a custom error. The catch statement allows you to define a block of code to be executed, if an error occurs in the try block.
The try and catch keywords come in pairs: We use the try block to test some code: If the age variable is less than 18, we will throw an exception, and handle it in our catch block. In the catch block, we catch the error and do something about it.
The catch statement takes a parameter: in our example we use an int variable myNum because we are throwing an exception of int type in the try block age , to output the value of age. If no error occurs e. For example, in the following program, an int is thrown as an exception, but there is no catch block for int, so catch … block will be executed. Skip to content.
Change Language. Related Articles. Previous Prev. Next Continue. Home Testing Expand child menu Expand. SAP Expand child menu Expand. Web Expand child menu Expand. Must Learn Expand child menu Expand. Big Data Expand child menu Expand. Live Project Expand child menu Expand.
0コメント