RE: [Cppunit-devel] CppUnit 1.8.0 features...

[Summerwill, B. <BSu...@eu...>]

Baptiste wrote:

>> I would actually call that one a bug fix. While const is usefull when 
>> manipulating value object, it is a strong constraint. Personnaly, I have
taken 
>> Michael Feather's advice on XP and C++ and don't use const on reference
object 
>> (object who don't have public copy constructor). This make refactoring a
lot 
>> easier, but writing assertion_traits black magic :-(.

Please could you clarify why you wouldn't want const references?  Maybe
provide
a link to Michael Feather's advice?

I've always found const-correctness very useful, and would see removing
const-correctness from CppUnit as a backwards step.  There are a number of
other
areas in the framework which I spotted as not being const-correct.  Is this
a
policy decision, that you aren't being const-correct?


Cheers,
Bob

-----Original Message-----
From: Baptiste Lepilleur [mailto:gai...@fr...]
Sent: 25 September 2001 11:40
To: Baptiste Lepilleur
Cc: Cpp Unit Develpment Mailing List
Subject: Re: [Cppunit-devel] CppUnit 1.8.0 features...


Quoting Baptiste Lepilleur <bl...@cl...>:

>     Depending on how soon you want 1.8.0 to be, here is a list of
> feature
> that are simple to implement:
> 
>     1) CPPUNIT_TEST_EXCEPTION( method, ExceptionType)
>     2) CPPUNIT_TEST_FAIL( method )
>     3) add a flag to TestFailure distinguishing error/failure, retain
> only
> one collection to store result
> (see other mail)
>     4) CPPUNIT_TEST_SUITE_NAMED_REGISTRATION( TestFixtureType, SuiteName
> ) :
> register the fixture's suite in a suite of the specified name.
>     5) Qt TestRunner (I've got it working, need feedback and help to
> use
> TMAKE to build a library instead of an application)
>     6) ASSERT_EQUAL support for two differents compatible types

      7) remove consteness on ASSERT_EQUAL. 
    I would actually call that one a bug fix. While const is usefull when 
manipulating value object, it is a strong constraint. Personnaly, I have
taken 
Michael Feather's advice on XP and C++ and don't use const on reference
object 
(object who don't have public copy constructor). This make refactoring a lot

easier, but writing assertion_traits black magic :-(.

      Baptiste.
   



---
Baptiste Lepilleur <gai...@fr...>
http://gaiacrtn.free.fr/index.html
Language: English, French

_______________________________________________
Cppunit-devel mailing list
Cpp...@li...
https://lists.sourceforge.net/lists/listinfo/cppunit-devel