exception-handling

In C++ you may declare function with exception specification like this: int foo() const throw(Exception); I found those two links: http://www.cplusplus.com/doc/tutorial/exceptions/ and http://publib.boulder.ibm.com/infocenter/lnxpcomp/v8v101/index.jsp?topic=%2Fcom.ibm.xlcpp8l.doc%2Flanguage%2Fref%2Fcplr156.htm But several things end up unanswered... Question 1: why to add exception specification? Will it bring any performance increase? What will be different for compiler? Because it seems just like an information for programmer to me. Question 2: what will happend (what should happen) if I

Before Consider to have a class and a global function: This is, for example, usefulfuncts.hpp void dosome(int a, int b) throw (std::exception); This is usefulfuncts.cpp void dosome(int a, int b) throw (std::exception) { //... } And this is aclass.hpp class aclass { // Members... friend void dosome(int a, int b) throw (std::exception); // Members... }; After (what I would like that to be) Ok! I would like to understand if it is strictly necessary to write everytime the throw clause. So for example can I do this? This is usefulfuncts.hpp void dosome(int a, int b) throw (std::exception); This is

In the code snippet below, why wouldn't the attached handler (of AppDomain.CurrentDomain.UnhandledException event) fire up when an exception is thrown in the unit test? I'm using NUnit 2.5.10 with TestDriven.NET 3.0 on VS2010. [TestFixture] public class MyTests { private void CurrentDomain_UnhandledException(object sender, UnhandledExceptionEventArgs e) { Console.WriteLine("Gotcha!"); } [Test] public void ExceptionTest1() { AppDomain.CurrentDomain.UnhandledException += CurrentDomain_UnhandledException; throw new Exception("ExceptionInTest"); } } Output: (No gotchas) ------ Test started:

Is it possible to navigate to another page/view from the constructor of the managed bean? I want this redirection if any exception occurred. I have tried many ways: Try-1: getFacesContext().responseComplete(); getFacesContext().getApplication().getNavigationHandler().handleNavigation(getFacesContext(), null, "gotoPartError"); getFacesContext().renderResponse(); Try-2: getServletResponse().sendRedirect("partError.jspx") Try-3: getFacesContext().responseComplete(); getFacesContext().getExternalContext().redirect(getServletRequest().getContextPath() + "/pages/partError.jspx"); Try-4: