Hi, Personally, I'd prefer not. I want the compiler to tell me if I invoke a private method. Also, I have to be sure that the tests are testing exactly the same thing as my apps are using, particularly with respect to templates.
If you need to test it, you can either extract the method or make it public static, or make a class called Midpoint and put the method in that, public static. The latter would be my preference (unless you can use std::binary_search). I guess if you can make it optional then it can be used, but I think it goes against UnitTest++ principles! Joel Clark Gaebel wrote: > 3. Should I even submit this? Has this already been talked out to death and > decided against? I wouldn't know. I'm new here ;) ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ unittest-cpp-devel mailing list unittest-cpp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
