On Nov 20, 8:09 pm, White Wolf <wo...@freemail.hu> wrote:
Paavo Helde wrote:
Regarding Google, maybe they might have banned exceptions because
of the run-time overhead (just guessing). Throwing exceptions is
notoriously slow, so they should not be used unless something
goes very wrong - but for a 24/7 service like Google nothing
should go wrong ever, so no need for exceptions, right?
Notoriously slow is a pretty vague statement. Exceptions do not
slower the speed of the code unless they are thrown. So your
choices are: slow your happy code (that runs a billion times) by
inserting hundreds of if statements into it to propagate return
codes up the call stack to the handler, or make returning 1000
times slower 3 times a day... It is a no brainer to me.
Sadly no. That was the intent. However, on half of all of the unix-
like environments available for me to test on, including Solaris,
AIX, HPUX, Linux, and for the common windows platforms, win32,
win64, exceptions add overhead even when not thrown, some worse
than others. Windows, for example, implements C++ exceptions on top
of their structured exception handling, which means that you're
paying a penalty every time you enter a try block.
Not that I'm trying to say use exceptions or don't in this post.
Just understand their practical costs and don't repeat (wishful)
misinformation.