throw

问题 This question already has answers here : how to throw an IOException? (7 answers) Closed 6 years ago . Code: catch (IOException e) { LOGGER.error("IOException exception happened"); //now need throw again the same exception to be //catched in the upper method } But when I try simply: catch (IOException e) { LOGGER.error("IOException exception happened"); //now need throw again the same exception to be //catched in the upper method throw e; } Eclipse supposes to me put "throw e" in try catch

问题 This is a retelling of my previous post, since I changed the question (so it probably didn't get flagged as a new question and was missed). I'll hopefully trim it down too. I had functions like: #include <cstddef> #include <type_traits> template < typename E, typename T > inline constexpr auto checked_slice( E &&, T &&t ) noexcept -> T && { return static_cast<T &&>(t); } template < typename E, typename T, std::size_t N, typename U, typename ...V > inline constexpr auto checked_slice( E &&e, T

问题 I am trying to write some C++ code (using the C++ API) for Festival and am getting stuck while trying to compile. Here is how I invoke g++ : g++ -Wall -pedantic -I../ -I../speech_tools/include/ helloFestival.C -o h -L../festival/src/lib/libFestival.a -L../speech_tools/lib/libestools.a -L../speech_tools/lib/libestbase.a -L../speech_tools/lib/libeststrings.a |& tee festival.runLog The error I get is: In file included from ../speech_tools/include/EST.h:48, from ../festival/src/include/festival.h

问题 I have problem with Spring framework, I was searching for solution long time, but any result. When I Deploying an application, I get Exception: 14.11.2012 0:37:23 org.apache.catalina.core.ApplicationContext log INFO: No Spring WebApplicationInitializer types detected on classpath 14.11.2012 0:37:23 org.apache.catalina.core.ApplicationContext log INFO: Initializing Spring root WebApplicationContext 14.11.2012 0:37:24 org.apache.catalina.core.StandardContext listenerStart SEVERE: Exception

问题 This is pretty much IE related because IE is the environment I'm using to test this, but I want to know if you can affect the relevancy of the error object properties when you throw an error. Consider the following javascript: function MyClass (Arg1, Arg2) // Line 5 of my.js { if (typeof Arg1 != "string") throw new Error("Invalid argument passed for MyClass"); // Do some other stuff here } Further down your code you have var myvar = new MyClass(100, "Hello"); // Line 3201 of my.js So the

问题 I have a unit test that tests if method throws an exception when condition is present, and method does throws exception as expected. - (void)testMethodThrowsWhenConditionIsPresent { XCTAssertThrows([Foo methodWithCondition: condition], @"Condition is true, method should throw exception"); } Here is the exception source: - (void)methodWithCondition:(someType)condition { if (condition) { [NSException raise: @"condition is true!" format: @"condition is true!"]; } } Why does the test stop at the

问题 #include <iostream> using namespace std; constexpr int f(bool b){ return b ? throw 0 : 0; } // OK constexpr int f() { return f(true); } // Ill-Formed, No Diagnostic Required int main(){ try{ f(); }catch( int x ){ cout << "x = " << x << endl; } return 0; } This code is an example from the C++14 Standard (ISO/IEC 14882:2014), Section 7.1.5, Paragraph 5: For a non-template, non-defaulted constexpr function or a non-template, non-defaulted, non-inheriting constexpr constructor, if no argument

问题 I am facing the famous 'Incorrect syntax' while using a THROW statement in a T-SQL stored procedure. I have Googled it and checked the questions on StackOverflow but the solutions proposed (and strangely, accepted) do not work for me. I am modifying a stored procedure as follows: ALTER PROCEDURE [dbo].[CONVERT_Q_TO_O] @Q_ID int = NULL, @IDENTITY INT = NULL OUTPUT AS BEGIN SET NOCOUNT ON; DECLARE @EXISTING_RECORD_COUNT [int]; SELECT @EXISTING_RECORD_COUNT = COUNT (*) FROM [dbo].[O] WHERE [Q_ID

问题 These days, I have been reading a lot the C++ F.A.Q and especially this page. Reading through the section I discovered a "technique" that the author calls "exception dispatcher" that allows someone to group all his exception handling in one handy function: void handleException() { try { throw; // ?! } catch (MyException& e) { //...code to handle MyException... } catch (YourException& e) { //...code to handle YourException... } } void f() { try { //...something that might throw... } catch (...

问题 Is it proper to use throw new FoobarException(Baz argument); or throw FoobarException(Baz argument); ? When catching I always use catch(FoobarException& e) "just in case" but I never could find a solid answer whether I had to use new or not in C++ (Java definitely) or if it was just a preference of the programmer. 回答1: Exceptions in C++ should be thrown by value, and caught by reference. So this is the proper way: try { throw FoobarException(argument); } catch( const FoobarException &ex ) {