Too Important

There are three people: Bob, John, and Jane.  Bob knows four languages, has won several state-wide competitions for giving speeches, and is an expert in ancient Egyptian culture.  John dropped out of college and knows nothing extraordinary other than how to outdrink everybody else where he attended college.  Jane is the CEO of a company that manages museums, and she is friends with John's mother (who is the CEO of a phone company).

Red-Black Trees

    This is a tutorial on coding red-black trees. I have tried to make it as easy to understand and detailed as possible. It covers both insertion and deletion from a red-black tree data structure.

Update: Tree Comparison on Hold, But Red-Black Tutorial Soon

Okay, I know that I promised a blog comparing AVL trees to red-black trees in a previous blog.  That blog was deleted since it may be a while.  I was planning on deleting it anyways if there were no comments since all of the information in it would be present and elaborated upon in the new blog about the comparisons.

A Container that Uses an Allocator

In a previous post, I explained how to make your own allocators.  But one question still remains: how can I make a container that uses the amazing tools that are allocators?  Normally, a person would not worry about such things because the STL has almost every kind of container that will be needed, but it does lack a few; for example, an ordered dictionary is not part of the STL.

Standard Allocator Problems

As I have mentioned before, I do not consider myself an expert on allocators, but I do know a little about them.  In a previous post I explained their purpose, and in a future post I plan to show how to make your own container that uses them.  If I am not an expert, though, what qualifies me to express my concerns about a problem I think that I found in the C++ standard concerning allocators?  Well, starting the topic should be fine, but I think that I will leave the actual "do something about it" to somebody with more experience in such things.

Funky Memory

Allocators.  They are terrifying, difficult to understand, and easy to misunderstand.  They do not seem to be coded often, and few articles are written about them.  There is little to go on to figure out what exactly those handy little tools do or even how to use them.

I do not consider myself an expert on the topic, but I have read many articles, perused thousands of lines of code that uses them, and read the C++ standard¹'s sections about them. I am not an expert, but I know a little about allocators, and a little more information on the Web is much better than none at all!

First Post

"First Post" is a cliché title for a first post, but it's fitting.  Don't you think?

As I am waiting on the clock to reach 1:00pm and for my French class to begin, I find myself contemplating the reasoning behind a few standard C++ specifications.  I have a complaint to make (which will be in a later post), and Facebook just does not seem to be the place for such ranting.  I hereby create this blog in order to publish my ideas and thoughts — not only about programming but about anything else that I believe should be shared or about anything that need not really be shared other than for the relief that comes with venting.