Comments on: 7.12 — Handling errors (assert, cerr, exit, and exceptions) http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/ Tue, 07 Feb 2012 12:30:29 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: newUser http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/comment-page-1/#comment-95331 newUser Fri, 15 Apr 2011 01:56:11 +0000 http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/#comment-95331 I'm still wondering how a good assert should be written. Like should it be written a line above a for statement while copying the statement's arguements? If this is correct, might we want to put this in the tutorial as a "best practices" while giving context to how it's written? I’m still wondering how a good assert should be written. Like should it be written a line above a for statement while copying the statement’s arguements? If this is correct, might we want to put this in the tutorial as a “best practices” while giving context to how it’s written?

]]> By: SWEngineer http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/comment-page-1/#comment-95124 SWEngineer Sun, 23 Jan 2011 11:28:21 +0000 http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/#comment-95124 Thanks for the tutorial. Shouldn't "GetValue(-3)" here under "Assert" be "GetArrayValue(-3)"? If the user calls GetValue(-3), the program prints the following message: ..... Thanks for the tutorial.

Shouldn’t “GetValue(-3)” here under “Assert” be “GetArrayValue(-3)”?

If the user calls GetValue(-3), the program prints the following message: …..

]]> By: Bob http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/comment-page-1/#comment-91392 Bob Sat, 04 Sep 2010 16:03:22 +0000 http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/#comment-91392 The actual file is obviously iostream.h, but when you include it it is <pre><iostream><!--formatted--></pre> You might wanna re-read the header file chapter. The actual file is obviously iostream.h, but when you include it it is 
<iostream>

You might wanna re-read the header file chapter.

]]> By: Tom http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/comment-page-1/#comment-90624 Tom Fri, 20 Aug 2010 22:15:14 +0000 http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/#comment-90624 If the user calls GetValue(-3), the program prints the following message: Should be GetArrayValue If the user calls GetValue(-3), the program prints the following message:

Should be GetArrayValue

]]> By: baldo http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/comment-page-1/#comment-66470 baldo Mon, 17 Aug 2009 14:28:36 +0000 http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/#comment-66470 You said: "<strong>cerr</strong> is an output stream (just like cout) that is also defined in iostream.h". It is iostream or iostream.h? You said: “cerr is an output stream (just like cout) that is also defined in iostream.h”. It is iostream or iostream.h?

]]> By: Fred Schneider http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/comment-page-1/#comment-64974 Fred Schneider Sat, 25 Jul 2009 03:26:23 +0000 http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/#comment-64974 <pre> // Delcare an array of 10 integers int *panData = new int[10]; // If something went wrong if (!panData) exit(2); // exit the program with error code 2 panData[5] = 3; </pre> This example is extremely outdated (1993 or so). Nowadays, new operators through a bad_alloc exception if it can't allocate the memory. So, it's not necessary to check if panData==0 but exception handling should be implemented somewhere in your code. If you don't catch the error, and you don't re-define the unexpected() or terminate() functions, your program will terminate anyways making the safety/correctness of the statement: panData[5]=3; irrelevant. // Delcare an array of 10 integers int *panData = new int[10]; // If something went wrong if (!panData) exit(2); // exit the program with error code 2 panData[5] = 3;

This example is extremely outdated (1993 or so).

Nowadays, new operators through a bad_alloc exception if it can’t allocate the memory. So, it’s not necessary to check if panData==0 but exception handling should be implemented somewhere in your code. If you don’t catch the error, and you don’t re-define the unexpected() or terminate() functions, your program will terminate anyways making the safety/correctness of the statement: panData[5]=3; irrelevant.

]]> By: Dusty http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/comment-page-1/#comment-64776 Dusty Wed, 22 Jul 2009 12:38:42 +0000 http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/#comment-64776 To answer that question Michel, it's good practice to put your own error handling in where ever possible. The error handling can be used to put the errors into terms that the end user can understand, not just the programmer. Error handling is not just good for debugging code, it's also good to help point out errors in live programs being used by a client or user. Alex THANK YOU FOR THIS ARTICLE!! I just sent it to a friend of mine who needed to see this, shall we say. ;) To answer that question Michel, it’s good practice to put your own error handling in where ever possible.

The error handling can be used to put the errors into terms that the end user can understand, not just the programmer.

Error handling is not just good for debugging code, it’s also good to help point out errors in live programs being used by a client or user.

Alex THANK YOU FOR THIS ARTICLE!! I just sent it to a friend of mine who needed to see this, shall we say. ;)

]]> By: Michel http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/comment-page-1/#comment-64150 Michel Sat, 11 Jul 2009 17:24:55 +0000 http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/#comment-64150 On Visual Studio 2008 Professional Edition, when an error is created, it states all the information in the Error List including which file and which line in that file the error occured. Therefore, do you need to use the assert() function when you are using VS 08 Pro? On Visual Studio 2008 Professional Edition, when an error is created, it states all the information in the Error List including which file and which line in that file the error occured. Therefore, do you need to use the assert() function when you are using VS 08 Pro?

]]> By: Tip C/C++: assert vs exception | La plaga Tux http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/comment-page-1/#comment-63844 Tip C/C++: assert vs exception | La plaga Tux Mon, 06 Jul 2009 22:51:49 +0000 http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/#comment-63844 [...] http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/ No olvides valorar la entrada - Ninguna votación aún :(  Loading ... [...] [...] http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/ No olvides valorar la entrada – Ninguna votación aún :(  Loading … [...]

]]> By: anwaar http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/comment-page-1/#comment-60545 anwaar Tue, 12 May 2009 01:15:06 +0000 http://www.learncpp.com/cpp-tutorial/712-handling-errors-assert-cerr-exit-and-exceptions/#comment-60545 no arjun! ur while is just for to check validity of positive numbers within the bound of lenght of declared string, but other one was also to check the either user has also entered a negative number. no arjun! ur while is just for to check validity of positive numbers within the bound of lenght of declared string, but other one was also to check the either user has also entered a negative number.

]]>