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.
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
It’s almost impossible without some understanding of the underlying code. If you understand the underlying code, then you can better sort the wheat from chaff of the zillion bits of information you are getting in your heap dumps. Also, you can’t know if something is a leak or not without know why the class is … Read more
Legacy code is a big issue, and I’m sure people will not agree! I would say that starting a big re-factor could be a mistake. A big re-factor means doing a lot of work to make it function exactly the way that it does now. If you choose to take this on on your own, … Read more
Read Michael Feather’s book “Working effectively with Legacy Code” This is a GREAT book. If you don’t like that answer, then the best advice I can give would be: First, stop making new legacy code[1] [1]: Legacy code = code without unit tests and therefore an unknown Changing legacy code without an automated test suite … 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
Start with some small task if possible, debug the code around your problem. Stepping through code in debug mode is the easiest way to learn how something works.
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