We use this to test software operating on VxWorks on an embedded platform. Exceptions don't work worth a damn on that particular version of VxWorks. So we modified the implemetation to avoid exceptions.
The question is, is there some fundamental reason why the implementation uses exceptions?
Also, the use of "assert" clashes with the normal C/C++ meaning of that usage. Is that intentional?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I know this post is about a year old, but I hope there still may be folks using CppUnit with vxWorks. We are interested to use this as well under vxWorks (for starters) and possibly other environments as well (desktop apps). I was wondering what had to be done to circumvent the usage of exceptions? Also, did you have any issues with the usage of vectors or other STL mechanisms?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-01-15
Yet another year passed....
I also wonder the same thing!!!
It should not really be necessary
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We use this to test software operating on VxWorks on an embedded platform. Exceptions don't work worth a damn on that particular version of VxWorks. So we modified the implemetation to avoid exceptions.
The question is, is there some fundamental reason why the implementation uses exceptions?
Also, the use of "assert" clashes with the normal C/C++ meaning of that usage. Is that intentional?
I know this post is about a year old, but I hope there still may be folks using CppUnit with vxWorks. We are interested to use this as well under vxWorks (for starters) and possibly other environments as well (desktop apps). I was wondering what had to be done to circumvent the usage of exceptions? Also, did you have any issues with the usage of vectors or other STL mechanisms?
Yet another year passed....
I also wonder the same thing!!!
It should not really be necessary
As an alternative, you might look at CxxTest (also here on SourceForge) which doesn't use exceptions.
http://cxxtest.sourceforge.net/