(no subject)

[logomancer]

Got back from Philly last nigh...er, this morning. We lost. Not surprisingly. I mean, we were up against some hardcore brains from UCLA, Chicago, and others. But I'm cool with it. They (the tournament guys) gave us all this swag. I now have a nice polo shirt and canvas bag. Nifty.

Since we didn't make the playoffs, we went home early. This gave me enough time to finish my project. Even though it works, it still throws a pair of exceptions at the end. Must ask McPherson about that tomorrow.

So, I'm just chilling out right now. No real exams to speak of, although I have a few tests coming up. I'll study for those later. It's so nice outside, I'm going for a walk...

Comments

[nius.livejournal.com]

Exceptions at the end eh?
My suggestion: Take a closer look at your destructor. At the end of the program, all your objects are destroyed and all your dynamically allocated memory is thrown back into the heap. If you're faulting at close it's probably due to a memory leak or a dangling pointer. Debugger is your friend :-)

[vt-andros.livejournal.com]

That's what I was thinking, Nius. But since deadline has passed and we're doing auto-grading(via Curator -- ask me how I feel about cutting and pasting all my code into one gargantuan CPP file), it has lost relevance. Unless I want to make a template out of it at some future date. Then I'll need to fix it.