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.
    Labels:

    Comments

    Post a Comment

    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: https://en.wikipedia.org/wiki/SOLID
    Post a Comment
    Read more

    Best Documentation of a Free Software Package

    One oft overlooked artifact in software development is the documentation. An API that is not well documented is no API at all when time is of the essence. That's why I think it is important to discuss some of the tools I have used and their documentation. AutoIt - I love how you simply press F1 within the AutoIt editor and boom, the reference to the particular syntax or function pops up in the help window. This help file is well written, self-contained, and chock full of examples that can be opened up in the editor right from the help, a fantastic symbiotic relationship. After installing AutoIt and giving it a try using their examples, I was able to create client/server scripts, GUI scripts, and window management scripts in no time. Overall, AutoIt is tops in this competition. A+ MySQL - At the bottom of each page of documentation that discusses a particular statement, users are able to post comments containing code snippets for that particular statement. This is great... M...
    1 comment
    Read more

    AWS Development On A Budget

    I was interested in hosting a small portfolio of applications in AWS, but I wanted to keep costs down.  I was willing to maybe host about $30-$40 a month of servers just to showcase some of the applications I was putting together.  Here's what I came up with. The basic capabilities here were: serve up about 6-10 applications that would require some level of web application hosting, database, file storage for larger items, and possibly queuing or email schedule jobs to run periodically to either scrape websites for new data or access APIs regularly These were the services in mind, all out of US-East-1 (Virginia): EC2 instances are pretty cheap.  You can run a t3a.nano for about $3.38 a month, or a t3a.micro for about double that for $6.77.  The more things can run on one of these instances, the better. Lambdas also don't really add up to much if they are scheduled jobs that do not consume large amounts of memory or computing.   The cost of a Lambda run as pa...
    Post a Comment
    Read more