Hey, I got into Mensa. That means I'm smart... psh. I heard a statistic that the average Mensan makes less than the average American. I wonder if that's true 
My C++ code is just about done, except when I resize() a vector, my data is getting screwed up. Turns out there's this statement on page 456 in Stroustrup (special edition):
When a vector is resized to accomodate more (or fewer) elements, all of its elements may be moved to new locations. Consequently, it is a bad idea to keep pointers to elements in a vector that might be resized; after resize(), such pointers could point to deallocated memory. Instead, we can keep indices.
And that's exactly what I'm doing. Why would it deallocate existing elements on resize? That causes my objects to be destructed and all their data to be freed, so there's nothing to put in the new location. And what does he mean by "we can keep indices"? Indices to what? I thought a pointer was an index
(to the place in memory where I'm keeping my object).
So... how do I do what I need to do?
Hmm... actually, I'm not keeping pointers in my vector... I'm keeping handles to objects. So the handle gets destructed and frees my memory, but if I keep pointers in there instead the pointers should just be copied, right? So now I have to rewrite all my vector code to use pointers to the handles to the objects? Grr! 
New record for weblogs.com - and this at 6 in the morning. 215 seconds!
I think I want to see Finding Nemo again. I just saw some clips of it on the news, and it's such a beautiful movie. If anyone's in the area who wants to come... 

I'm watching Mr. T preaching right now on TV. Yes, Mr. T. He's awesome.
The Elegant Universe
Well I have finally found the crazyguy that preaches useless nonsencein A...
Joseph Baxter: Jan 7, 11:07pm