¡@
c++ Programming Glossary: revealvisual studio 2008 solution release version runtime fatal error http://stackoverflow.com/questions/12800777/visual-studio-2008-solution-release-version-runtime-fatal-error be doing this all the time anyways. This will very often reveal the problem. Just be sure to fix the problems the compiler tells..
http://stackoverflow.com/questions/1598703/profiling-dll-lib-bloat symbol. Using a strings utility to scan your DLL might reveal unexpected or unused printable strings e.g. resources RCS IDs..
How to analyze program running time http://stackoverflow.com/questions/18194577/how-to-analyze-program-running-time the deal There are ways to speed up your code that do not reveal themselves as slow functions or hot paths for example reorganizing.. even if it has high inclusive time percent. They do reveal themselves if you actually look at stack samples . So the problem..
SFINAE: checking the existence of a function breaks when the overload is moved to other namespaces http://stackoverflow.com/questions/18933857/sfinae-checking-the-existence-of-a-function-breaks-when-the-overload-is-moved-t the enclosing namespace. The details from namespace.udir 2 reveal the issue ... During unqualified name lookup 3.4.1 the names..
Critique my non-intrusive heap debugger http://stackoverflow.com/questions/2835416/critique-my-non-intrusive-heap-debugger question Very nice indeed. Your canaries could actually reveal some real cases of overflow underflow though not all of them..
http://stackoverflow.com/questions/32168/c-cast-syntax-styles are intentionally visually striking. Since casts often reveal a weakness in the code it's argued that making casts visible..
http://stackoverflow.com/questions/366228/def-files-c-c-dlls if you export some functions only by ordinal which doesn't reveal as much information about the function itself eg many of the..
Beyond Stack Sampling: C++ Profilers http://stackoverflow.com/questions/4394606/beyond-stack-sampling-c-profilers a stack trace every N instructions. This technique will reveal portions of your code that are CPU bound. Which is awesome if..
Exceptions and error codes: mixing them the right way http://stackoverflow.com/questions/5805410/exceptions-and-error-codes-mixing-them-the-right-way that make the code full of hidden bugs that hard to reveal. Exceptions make error handling isolated. If you need to handle..
Switch from Microsofts STL to STLport http://stackoverflow.com/questions/604050/switch-from-microsofts-stl-to-stlport any performance improvements Even if profiling does reveal performance issues in standard library containers or algorithms..
Measuring NUMA (Non-Uniform Memory Access). No observable asymmetry. Why? http://stackoverflow.com/questions/7259363/measuring-numa-non-uniform-memory-access-no-observable-asymmetry-why inside my innermost loops. It still doesn't reveal any asymmetry between NUMA nodes. Update 2 I've tried reading..
List of C++ name resolution (and overloading) rules http://stackoverflow.com/questions/7374588/list-of-c-name-resolution-and-overloading-rules two cases do not. Simply glancing at the Standard will reveal many exceptions and gotchas. For example unqualified lookup..
How should I detect unnecessary #include files in a large C++ project? http://stackoverflow.com/questions/74326/how-should-i-detect-unnecessary-include-files-in-a-large-c-project share improve this question While it won't reveal unneeded include files Visual studio has a setting showIncludes..
Finding out the CPU clock frequency (per core, per processor) http://stackoverflow.com/questions/8351944/finding-out-the-cpu-clock-frequency-per-core-per-processor the request of the XtremeSystems Forums admins I will not reveal how to do this. They have taught me some of the most powerful..
Using SendMessage to enter text into an edit control belonging to another process http://stackoverflow.com/questions/9984770/using-sendmessage-to-enter-text-into-an-edit-control-belonging-to-another-proces edit WM_CHAR ... PostMessage edit WM_KEYUP ... Spy will reveal what the other parameters are don't worry. You will probably..
|