throw

What does C++ standard say should happen for the following code when there is no pending exception being processed higher up the stack? try { throw; } catch (...) { cerr << "Caught exception." << endl; } Will the throw with no object be caught or not? From the 2003 C++ Standard §15.1[except.throw]/8: If no exception is presently being handled, executing a throw-expression with no operand calls terminate() . So, in your example, since no exception is currently being handled, nothing is thrown and instead terminate() is called. Since terminate() does not return, your catch block will never be

I know this is a weird on, but in my code, i have development mode errors, and production mode errors. This is the function i have: private function error($message, $mysql_error = null){ if( DEVELOPMENT_MODE ){ $exp = new Exception(); $trace = $exp -> getTrace(); array_shift( $trace ); // removes this functions from trace $data["Error Mg"] = $message; $data["MySQL Er"] = ( is_null ( $mysql_error ) ) ? "" : $mysql_error; array_unshift($trace, $data ); fkill( $trace ); // formats array and then dies } else{ throw new Exception ( $data ); } } I wrote this function in my database class, so that if

SQL Server 2008 R2 Management Studio does not recognized my throw in the below example, it says incorrect syntax near Throw I am trying to throw an error here, so I can handled it in my website when someone insert the same value twice. Begin Try insert into BusinessID (BusinessID) values (@ID) insert into BusinessID (BusinessID) values (@ID) End Try Begin Catch Print 'PK already exist' THROW End Catch THROW Statement is introduced in SQL Server 2012 http://msdn.microsoft.com/en-us/library/ee677615.aspx You can use RAISERROR instead. http://msdn.microsoft.com/en-us/library/483588bd-021b-4eae

I'd like a response from someone who actually does real-time programming in C# or who really understands the language internals. I know that exceptions should not be used to handle normal processing, but only to detect error conditions. There is plenty of discussion on that topic. I'd like to know if there is any run time slow-down from simply having a try/catch block in place (which never catches an exception unless the program will have to end anyway). The try/catch block is inside a function which must be called repeatedly. I suspect there is only minimal cost. Can the cost be quantified in

I'm writing a custom class in C# and I'm throwing a couple exceptions if people give the wrong inputs in some of the methods. If the exception is thrown, will any of the code in the method after the throw still be executed? Do I have to put a break after the throw, or does a throw always quit the method? When you throw an exception, the next code to get executed is any catch block that covers that throw within the method (if any) then, the finally block (if any). You can have a try, a try-catch, a try-catch-finally or a try-finally. Then, if the exception is not handled, re-thrown by a catch

This question already has an answer here: Is there a difference between “throw” and “throw ex”? 10 answers Can anyone tell me difference between throw and throw ex in brief? I read that throw stores previous exceptions, not getting this line. Can i get this in brief with example? Yes - throw re-throws the exception that was caught, and preserves the stack trace. throw ex throws the same exception, but resets the stack trace to that method. Unless you want to reset the stack trace (i.e. to shield public callers from the internal workings of your library), throw is generally the better choice,

I noticed by accident that this throw statement (extracted from some more complex code) compiles: void foo() { try { } catch (Throwable t) { throw t; } } For a brief but happy moment I thought that checked exceptions had finally decided to just die already, but it still gets uppity at this: void foo() { try { } catch (Throwable t) { Throwable t1 = t; throw t1; } } The try block doesn't have to be empty; it seems it can have code so long as that code doesn't throw a checked exception. That seems reasonable, but my question is, what rule in the language specification describes this behavior? As