xdebug‘s code coverage tools allow you to test which lines of code are actually being executed, without needing to put trace statements in all of the functions/methods. Example: <?php xdebug_start_code_coverage(); function a($a) { echo $a * 2.5; } function b($count) { for ($i = 0; $i < $count; $i++) { a($i + 0.17); } } … Read more
std::stringstream may be what you’re looking for. UPDATE Alright, this is a bit of hack, but maybe you could do this to grab the printf output: char huge_string_buf[MASSIVE_SIZE]; freopen(“NUL”, “a”, stdout); setbuf(stdout, huge_string_buffer); Note you should use “/dev/null” for linux instead of “NUL”. That will rapidly start to fill up huge_string_buffer. If you want to … Read more
The best way, I have found, is to incrementally add the unit tests, not to just jump in and say we will now unit test the application. So, if you are going to touch the code, for bug fixes or refactoring, then first write the unit tests. For bugs unit tests will help prove where … Read more
VB6 Installs just fine on Windows 7 (and Windows 8 / Windows 10) with a few caveats. Here is how to install it: Before proceeding with the installation process below, create a zero-byte file in C:\Windows called MSJAVA.DLL. The setup process will look for this file, and if it doesn’t find it, will force an … Read more
Sounds like a weird requirement… Anyway, reflection does not allow you to change code behaviour, it can only explore current code, invoke methods and constuctors, change fields values, that kind of things. If you want to actually change the behaviour of a method you would have to use a bytecode manipulation library such as ASM. … Read more
You could use a code coverage analysis tool for this and look for unused spots in your code. A popular tool for the gcc toolchain is gcov, together with the graphical frontend lcov (http://ltp.sourceforge.net/coverage/lcov.php). If you use gcc, you can compile with gcov support, which is enabled by the ‘–coverage’ flag. Next, run your application … Read more
From the ’89 standard as quoted in the new testament: Flowing off the end of a function is equivalent to a return with no expression. In either case, the return value is undefined. That standard usually expresses the on-the-ground behavior of pre-existing implementations.