If I use try/catch in WindowProc override of MFC window/view classes there is a performance hit. Why is it so and what is the alternative ?
This I caught as a result of profiling. Removing the block makes the function consume much lesser time. I am using MS VS 2008.
In usage-of-try-catch-blocks-in-c Todd Gardner explains that compilers use the “table” approach or the “code” approach to implement exceptions. The “code” approach explains the performance hit.