games.greggman.com

You might have known this but I just found this out yesterday.

I knew std::remove doesn’t actually remove anything. The way it is used goes something like this.

std::vector int_array;

int_array.push_back(1);
int_array.push_back(1);
int_array.push_back(1);
int_array.push_back(2);
int_array.push_back(3);
int_array.push_back(4);

// call remove to remove all the elements that equal 1
// remove reorders all elements so that the things you
// want removed are at the end of the vector
std::vector::iterator erase_from = std:remove(int_array.begin(),
                                                   int_array.end(),
                                                   1);

 Read more...

This topic seems almost too basic to even discuss but I’ve run into these issues fairly often so appearently they do need discussion

When coding somethings to keep in mind, how can we code both efficiently and defensively. In other words, how can we get things done faster and with less bugs.

Here’s a few ideas. They might seem obvious but like I said, I see lots of code that doesn’t follow these ideas and so I’m bringing them up.

#1) If you do something a lot, figure out a way to make it easier to do.

Here’s two examples from my own experience. I have a library to read .ini files. .Ini files are something that Windows first introduced me to. They are a very simple text based format that look something like this

Read more…

I’m not familiar with more than a few debuggers, but, the ones I use generally have an issue with single line member functions. Read more…