Skip to main content

Effective C++, Third Edition

"...much as in real life, friends are often more trouble than they're worth."
- Scott Meyers

The C++ type definition that declares an external function of a class as one that can access private or protected data members also defines an individual in which one confides. But are programming books less trouble than friends? I'd like to think so.

This book opened my eyes to angles of C++ that I had not considered in the past. In a summarized list, here were the parts I found most useful:

  • RAII (Resource Acquisition Is Initialization), defined in Item 13, states that it is easier to allocate resources simply by allowing their critical work to occur in the constructor/destructor rather than their functions. The example is the Mutex class, which is defined at the top of critical section functions, and that's it. It's easier than a call to it's lock() function and will clean itself up when the function completes.

  • Smart pointers, like std::auto_ptr or tr1::shared_ptr, are a great way to keep track of objects created on the heap. The decision of which of these pointers to use depends on whether the actual pointer should be copied or not on smart pointer assignment.

  • Forget exceptions, as noted in Item 29, or at least make your code exception safe. This prevents code from calling unhandled exceptions and causing the state of the program to go unknown. Exception safe code is accomplished through three guarantees: basic, strong, and nothrow.

  • Generic programming and Template MetaProgramming (TMP). This is really interesting stuff that I have seen before but had no clear references. Though lots of code can't be determined at compile-time, this still has some very interesting uses like pointer arithmetic.

  • Placement new and delete operators, and memory management strategies.

  • At this point, you might be thinking, "this guy sure must be busy with lots of work in C++ in order to be doing all this reading." In actuality, I'm hardly doing any C++ these days. I've read Effective C++ for the purpose of understanding what has been done around uses of the C++ programming language (with which I am very familiar) so that I can understand language issues that plague all OO languages.


    Popular posts from this blog

    Software Design Principles - SOLID

    The SOLID software design principles weren't called SOLID while I was in grad school, but the concepts were there in my Object Oriented Design course. They're worth mentioning here, primarily because I think once you start coding and become dangerous, it's one of the best ways to stay organized once you incorporate it into your daily coding routines, and it even changes your way of thinking for the better:

    Matlab and MySQL

    I had a lot of data in a MySQL database that I wanted to analyze. I had a copy of Matlab, so I figured the best way to look at this all would be to plot this data and use some GUI elements to go through various combinations. After some Googling, I found this database connector that seemed to do the trick. I downloaded the files, configured mex to use MSVC 2008, built the connector, then I was able to successfully connect over the network! I ran into two problems, though: The connector does not support fetching columns of type TIMESTAMP, and With the magnitude of data (about 180k rows), access times were really slow. I was able to solve problem #1 by changing my columns to DATETIME, which was supported. I'm still trying to figure out problem #2. It may come down to importing all the data directly into Matlab.

    The TL;DR guide to git

    While in the past I've held a pretty high opinion to using mercurial for version control, the majority of version control these days seems to done in git.  Here were the commands I found most useful to get productive with git right away. # Clone a repository from an origin, i.e. my github MaskingUtils repository git clone # Add a file after it's been updated to stage it for commit, or add a new file git add filename # Commit the file to local repo git commit # Push the file to the origin so the rest of the team can see it git push # List all locally tracked branches git branch git branch --list # Get a list of all branches from the remote git branch -r # Create branch locally git branch develop # Push the branch to the origin repository to make sure it is tracked there git push --set-upstream origin develop # Pulls latest from all local branches tracked from origin; won't pull non-tracked branches git pull --all # Fetch the branch