Catch std::exception& instead of std::runtime_error&

mrtrizer · web-flow · commit f5532d37068e · 2018-07-10T14:59:20.000+03:00
Currently, if any standard exception inherited form `std::exception` will be thrown (like `std::bad_alloc`), the program will be terminated without explanation.
May be there are objective reasons to catch exceptions that way, but this is not obvious for me.
Thanks!
diff --git a/03_Drawing_a_triangle/00_Setup/00_Base_code.md b/03_Drawing_a_triangle/00_Setup/00_Base_code.md
@@ -39,7 +39,7 @@ int main() {
 
     try {
         app.run();
-    } catch (const std::runtime_error& e) {
+    } catch (const std::exception& e) {
         std::cerr << e.what() << std::endl;
         return EXIT_FAILURE;
     }
@@ -63,7 +63,7 @@ Once the window is closed and `mainLoop` returns, we'll make sure to deallocate
 the resources we've used in the `cleanup` function.
 
 If any kind of fatal error occurs during execution then we'll throw a
-`std::runtime_error` exception with a descriptive message, which will propagate
+`std::exception` exception with a descriptive message, which will propagate
 back to the `main` function and be printed to the command prompt. One example of
 an error that we will deal with soon is finding out that a certain required
 extension is not supported.
