Skip to main content

The C++ Standard Library: Recap

The final 7 sections of The C++ Standard Library by Josuttis required lots of attention, but I am glad to have read this book cover to cover.

This book is worth purchasing for Chapter 8 alone in its description of the function objects. The concept of stateful function objects is a powerful idea and can be used in conjunction with the standard library algorithms to produce some powerful behavior.

Function objects provide a great introduction to the algorithms section in that many of the algorithms require function pointers or objects as arguments to execute on the item. Items in a container are typically modified using beginning and end iterators, or even pointers to contiguous arrays of memory.

After the algorithms section, a special containers section described the bitset container. This is a container that will come in handy during protocol development at some point, but whether operations on the bitset are faster than simple C binary operations would be interesting to test.

In the numerics section, the valarrays section proves to be a very interesting way to perform operations on vectors and matrices, and I'm surprised it's not used more often.

To make code internationalized, locales, character traits, and facets were described. I guess this doesn't mean too much to me at the moment since I only operate in the default C locale, but this is a good section to know when developing software for just about anywhere else in the world!

I am surprised the allocator section was so short. The section really only contained an instance of an allocator object along with several built-in C++ functions dealing with memory that has not been allocated (pointer to pointers) or constructed (actual objects). Maybe I will need to get my memory fix through some boost documentation or the books by Scott Meyers.

I also thought that it was interesting to know that folks in Nepal use 10.00.000 to represent 1,000,000.

Comments

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

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 git@github.com:caelumvox/masking-utils.git # 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

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 part of an API gateway