Re: Ranking of OO refactorings

In article <CAJifdbf6=rCETExMLm-6zGtWBzkjobuEE4LghvWjYo2NhMfx=Q@mail.gmail.com>,
    atulDOTkhotATGmailDOTcom <[email protected]> writes:

> I would add
>            Introduce Asserion
> Can't even count how many hours it saved for me ;-)

I haven't used this much and I have a specific reason why for C++.

Generally I prefer to work using TDD and when I have assertions firing
in my code, I can't test what happens beyond the assertion in debug mode,
but it would test beyond the assertion in release mode.  So I've come
to prefer throwing exceptions for (exceptional!) error handling over
assertions because I can unit test exceptions and I get the same
behavior in debug and in release.

If the system under test was performance critical code where even the
overhead of exceptions was not acceptable, then I would test it
another way.
-- 
"The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline>
     The Computer Graphics Museum <http://computergraphicsmuseum.org>
         The Terminals Wiki <http://terminals.classiccmp.org>
  Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/refactoring/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/refactoring/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/