Rupert many thanks for you answer. Unfortunately my intention was to make it without running the exe and then recompile. What you explain seems to me like a scripting interface, which I still can use when rely on perl or anything else. But you bring me to an idea, that I can do pre-build steps, like copying the cpp-file with internal linkage X-times and then compile all files copied. Actually the best solution for my would be to handle all these issues by a preprocessor. Many thanks, Ovanes On Fri, Apr 18, 2008 at 6:42 PM, Rupert Bruce wrote:

Ovanes Markarian wrote:

Hello *,

I have a question regarding testing. I would like to test my implementation how it bahaves in multi-threaded environment within different compilation units. Does anyone have ideas how I can generate from my c++ project (no perl or other scripting tools) (possibly with preprocessor ??) multiple compilation units in an automated way.

Many thanks, Ovanes

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

_______________________________________________ Boost-users mailing listBoost-users@lists.boost.orghttp://lists.boost.org/mailman/listinfo.cgi/boost-users

Your C++ code can simply write a testcase.cpp file for you. I use this for testing modifications to a model - I have an old but dependable model which writes test cases when I set a flag in my properties file. Most of the file is static strings, the parts that change are input parameters and results. I then rebuild (make automatically picks up the extra cpp files) the new model and the test cases are run at startup. BTW, I use UnitTest++ because it works and I haven't had a need to change...

Cheers Rupert

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users