![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
One Thing Leads to Another
Sep. 21st, 2011 11:34 pmSo I finally got the locking fixes that I made to compile. Now, I need to get everything to work again, which means that I'm testing various functions to make sure that they're alive.
Of course, many of them weren't on the first try. Some died because I inadvertently typed the wrong function name when I had a read lock on the object, so I got a NULL pointer exception. This is actually good, because it means that the least bit of unit testing will detect an attempt to write an object with a read lock.
It's just annoying to be hoist by my own petard given how much code I had to rewrite. Mistakes were pretty much guaranteed. :)
Of course, many of them weren't on the first try. Some died because I inadvertently typed the wrong function name when I had a read lock on the object, so I got a NULL pointer exception. This is actually good, because it means that the least bit of unit testing will detect an attempt to write an object with a read lock.
It's just annoying to be hoist by my own petard given how much code I had to rewrite. Mistakes were pretty much guaranteed. :)