From: H. H. <hen...@gm...> - 2008-08-27 19:59:54
|
ATM I am still in the process of writing test cases and correcting minor bugs in the GLM. The current implementation holds that the behavior is undefined if you pass NULL as function arguments: glmMatInverse2f (&foo, NULL); // BOOM I use assert's in the implementation to test this. However CUnit does not have a way to override the assert inside the function glmMatInverse2f: GLMmat2f * glmMatInverse2f (GLMmat2f *out, const GLMmat2f *m) { ... assert (out); assert (m); ... } And there cannot be because assert is usually defined as a macro. On Wed, Aug 27, 2008 at 8:22 PM, Orhun Birsoy <orh...@gm...> wrote: > pudman > OK, you convinced me for including such cases (asserts) in unit tests. > Thanks... > > One question though, will CUnit be able to override the assert in that > function so that the tests can continue? > > -- > Orhun Birsoy > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Glsdk-devel mailing list > Gls...@li... > https://lists.sourceforge.net/lists/listinfo/glsdk-devel > > -- Henri 'henux' Häkkinen |