{"id":4334,"date":"2013-10-07T05:00:30","date_gmt":"2013-10-06T18:00:30","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/wordpress\/?p=4334"},"modified":"2013-10-07T05:00:30","modified_gmt":"2013-10-06T18:00:30","slug":"c-xcode-oop-exceptions-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/c-xcode-oop-exceptions-primer-tutorial\/","title":{"rendered":"C++ Xcode OOP Exceptions Primer Tutorial"},"content":{"rendered":"
\"C++<\/a>

C++ Xcode OOP Exceptions Primer Tutorial<\/p><\/div>\n

Our C++ Xcode OOP Exceptions Tutorial presented here opens the door to the idea of handling error exceptions when using C++. The two major areas I’ve found where error handling is really important are with mathematical calculations and with input\/output scenarios (which includes file handling). Let’s see below some information about Exception Handling from Wikipedia:<\/p>\n

Exception handling is the process of responding to the occurrence, during computation, of exceptions \u2013 anomalous or exceptional events requiring special processing \u2013 often changing the normal flow of program execution. It is provided by specialized programming language constructs or computer hardware mechanisms.<\/p>\n

In general, an exception is handled (resolved) by saving the current state of execution in a predefined place and switching the execution to a specific subroutine known as an exception handler. If exceptions are continuable, the handler may later resume the execution at the original location using the saved information. For example, a floating point divide by zero exception will typically, by default, allow the program to be resumed, while an out of memory condition might not be resolvable transparently.<\/p>\n

Alternative approaches to exception handling in software are error checking, which maintains normal program flow with later explicit checks for contingencies reported using special return values or some auxiliary global variable such as C’s errno or floating point status flags; or input validation to preemptively filter exceptional cases.<\/p><\/blockquote>\n

Click on picture to see some C++ using XCode<\/a> programming showing an error handling scenario where we act in a proactive way to circumvent any errors to do with finding the cube root of a negative number (using the throw<\/a> method), and then looking at two mathematical checks which are not error throwers (via use of isnan<\/a> and isinf<\/a>) leaving default try\/catch exception logic<\/a> for other scenario types.<\/p>\n

Link to some downloadable programming C++ source code … rename to main.cpp<\/a> for use.<\/p>\n

Link to Exception Handling information … from Wikipedia from which quote above comes<\/a>.<\/p>\n

If this was interesting you may be interested in this<\/a> too.<\/p>\n