Re: [Cppunit-devel] TestSuiteBuilder & type info...

[Baptiste L. <gai...@fr...>]

Quoting Bastiaan Bakker <bas...@li...>:

> Baptiste Lepilleur wrote:
> 
> OK, finally I start to understand what you mean! :-)
> I've mostly been doing Java programming the last few years. No generics
> there,  so
> I'm not too intimate with those and some other C++ features.
> Thanks for the C++ Journal link. Interesting information, the author is
> pretty
> sick bastard though: calling writing a dozen basic_string
> implementations 'fun'
> :-D
> I must be a C++ wimp ;-)
  Well, I discovered this aspect of generic programming not so long ago and I 
see unit testing as a perfect way to solve many of the problems I have when 
pushing template this far (compilation error that appear only when you us the 
method, testing...). That's why I pushing that aspect forward.

> I don't care what people do on their own projects: they should be free
> to keep any
> platform dependencies they want.
> My worry is that the more platform dependent features get into CppUnit
> the more
> difficult it becomes to maintain:  people on other platforms cannot
> check whether
> they break these features, more code than neccessary may come to depend
> on it,
> etc. ,etc.
  From what you said it is possible to compile with RTTI enabled for g++. Even 
if the result is not readable, knowing that it compile is a first step.
  I added a configuration to compile without RTTI on VC++, that's how I 
discovered that the AutoRegisterSuite did not work (that's fixed now). You 
could do the same for Unix.

  I was thinking of doing unit test to test cppunit. I once found the test 
cases for Junit, but I looked for them and couldn't find them !

  Such unit tests would allow us to test the many aspects of cppunit ;-) (the 
current example barely skim the surface).

> OK, do what's necessary for the RTTI features. Now that I understand how
> it may be
> useful, I would not want to keep excluding it from the project.
  This is in CVS now.

> 
> Indeed, it isn't. I'll see if I can get the reasoning behind from one of
> the g++
> folks.
  Yes that would be interesting. 

> > you are doing multiplatform. We just have to stick it somewhere in the
> > documentation (I'll put it in TestSuiteBuilder at the current time).
> But I
> > would put it somewhere else. This fact is binded to the
> CU_USE_TYPEINFO macro,
> > not TestSuiteBuilder. Any Suggestions on where to put that ?
> >
> 
> With the TypeInfoHelper class?
  Yes I'll put it there for now, but It's buried pretty deep. I would like to 
have something more like a build guide that say "using CU_USE_TYPEINFO you can 
do this and that, but you lose multiplatform." I doubt the user would bother 
reading each class documentation. He doesn't even use TypeInfoHelper.
  
Baptiste.

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