Pinching an inch off of code-bloat
Here is a tool that looks quite interesting: SymbolSort
Here is a tool that looks quite interesting: SymbolSort
What!? LLVM is available for Visual Studio? http://llvm.org/docs/GettingStartedVS.html
Microsoft has a plug-in for Visual Studio that adds a lot of nice little features that I never realized I needed… like triple clicking to select a whole line.
I was introduced to Cyclomatic Complexity at Eric Rimbley’s course at Construx; I was facinated with the topic and found a tool that works with Visual Studio 2010 that gathers this metric: http://www.blunck.info/ccm.html
There used to be a button that would toggle you between the header file and implementation file that currently had the focus in Visual Studio. For reasons unknown to me, that feature was taken out in Visual Studio. Here is a macro though that brings that functionality back: I want my toggle button back!
Within a Visual Studio C++ solution, you can copy a file to a known location as part of the build process. To do that, you have so set the “Custom Build Step” parameters found in the Visual Studio project’s property page: Command line: copy “$(InputPath)” “$(TargetDir)” > nul Description: Copying $(InputFileName) Outputs: $(TargetDir)$(InputFileName) Note, the … Read more
This is a good reference for me since I have to do this on occasion when I switch from my Mac to my PC to do some general coding work: Enabling Memory Leak Detection
Today, I began using regular expressions to change a whole bunch of code. However, what I learned from using RegEx in TextMate was not the same as in Visual Studio. So, for example, the parenthesis around regular expressions to indicate a backreference in TextMate: (\w+) is represented by curly braces in VS: {\w+} And to … Read more
For the past 3 1/2 years, I have used Xcode almost solely for my development work, but, recently, I have switched over to Visual Studio to use some of the nifty tools that Intel has for performance profiling. The folks over at Microsoft have some nifty bloggers and one of them have this cool chart … Read more
To prevent Visual Studio from defining it’s own min and max functions, include the following in the top of your implementation file: #ifdef _WIN32 #ifndef NOMINMAX #define NOMINMAX #endif #endif You can also define NOMINMAX in the Preprocessor Definitions option in the Common Properties->C/C++->Proprocessor property page.