Re: Why do some code bases don't use exceptions?

From:

legalize+jeeves@mail.xmission.com (Richard)

Newsgroups:

comp.lang.c++

Date:

Thu, 26 Nov 2009 01:44:52 +0000 (UTC)

Message-ID:

<hekmik$cma$1@news.xmission.com>

[Please do not mail me a copy of your followup]

"Alf P. Steinbach" <alfps@start.no> spake the secret code
<hekgtv$un9$1@news.eternal-september.org> thusly:

* Richard:

[Please do not mail me a copy of your followup]

"Alf P. Steinbach" <alfps@start.no> spake the secret code
<hejsud$83s$1@news.eternal-september.org> thusly:

* James Kanze:

Yes, but having to write a try block, then a catch statement, is
more complicated than an if, if you want to process the error
immediately. You can use an exception, but it's about like
pealing a grape with a butcher's cleaver.

Off the cuff,

#define CATCHX( result, f, args ) \
    do { \
        try { \
            result = f args; \
        } catch( std::exception const& x ) { \
            result.set_x( x ); \
        } \
    } while( false )

....which is a good example of why macros are evil.

Mostly macros are evil, but your comment for this case makes no sense to me.

Would you care to elaborate a bit on exactly what you mean (if anything).

Macros hiding loops, returns or try/catch blocks are evil IMO.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>

Legalize Adulthood! <http://legalizeadulthood.wordpress.com>