Woke up this morning from a nightmare: my newly created custom clipboard object for work.project.name was leaking memory. Get to work, fire up the IDE, and sure enough, there’s the bug. I work too hard.
Some of you may be wondering how to cause memory leaks in Visual Basic, of all things. Parent pointers.
A related topic that has been bugging me lately is how to architect and write large (~30Kloc), complex programs in VB. work.project.name seems extremely complex to me, and no matter how well I attempt to compartmentalize the app by breaking it into COMponents, it still seems like too much. I’ve been doing this for long enough, yet it doesn’t seem to get any easier. The worst part is, I can’t figure out why it doesn’t seem to get any easier.