Blame doc/FAQ

Packit Service e31359
Frequently Asked Questions:
Packit Service e31359
---------------------------
Packit Service e31359
Packit Service e31359
1) Questions relating to CppUnit
Packit Service e31359
   ----------------------------
Packit Service e31359
Packit Service e31359
1.1) Isn't there an easier way to write unit tests than using TestCaller ?
Packit Service e31359
Packit Service e31359
   Yes, there is. Macros have been created to take care of the repetitive 
Packit Service e31359
work. Look up include/extensions/HelperMacros.h in CppUnit documentation. 
Packit Service e31359
Most of CppUnit test suite is also written that way since they remain 
Packit Service e31359
compatible as CppUnit evolve.
Packit Service e31359
Packit Service e31359
Packit Service e31359
2) Questions related to Microsoft Visual VC++
Packit Service e31359
   -----------------------------------------
Packit Service e31359
Packit Service e31359
2.1) Why does the compiler report an error when linking with CppUnit library?
Packit Service e31359
Packit Service e31359
   You most likely are not using the same C-RunTime library as CppUnit.
Packit Service e31359
   In Release configuration, CppUnit use "Mulithreaded DLL".
Packit Service e31359
   In Debug configurations, CppUnit use "Debug Multihreaded DLL".
Packit Service e31359
   Check that Projects/Settings.../C++/Code Generation is indeed using
Packit Service e31359
the correct library.
Packit Service e31359
   
Packit Service e31359
2.2) Why does CppUnit generate warning 4786:... when compiling ?
Packit Service e31359
Packit Service e31359
   I really don't have a clue. All CppUnit's headers starts by either
Packit Service e31359
including Portability.h or another CppUnit's header. Portability.h includes
Packit Service e31359
config-msvc6.h which disable that specific warning. The warning is generated
Packit Service e31359
by TestFactoryRegistry::m_factories. A solution to this problem is welcome.