(No Title)
I found a cool memory leak spotter: Valgrind. Free software and all that.
Looks like Python’s a bit leaky, but that’s to be expected. However, it spotted some stuff in Sigma (stuff I’ve been suspecting anyway), and I apparently have a segfault bug I didn’t know about. So, the project will go on the operating table after finals for a code clean.
I’m afraid my mistakes are going to get shoved up my butt at a later date if I don’t do something about them now. I wouldn’t use “disaster” to describe my object handling, but “suddenly more complex” is pretty accurate. About time for an audit.
It’s mainly the ManagedList objects I have now, which are doubly-linked lists with memory allocation built in. It’s a bit of a mess right now.
Oh well.