Bill Roper (billroper) wrote,
Bill Roper

One Thing Leads to Another

So 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. :)
Tags: musings, work

  • Time for Rebuilding

    Well, there's nothing like research. Having determined that DDR5 is going to carry a substantial price premium over DDR4 memory for at least a year…

  • Driven Wild

    The studio computer continues to misbehave in various ways. When I fired up Cubase today, I got a lot of nasty, blocky video, despite having cleaned…

  • Some Old Doggerel

    I recall having mangled a CSN tune many years ago on the way to Contraption. Like that convention, the particular co-worker whose code I was digging…

  • Post a new comment


    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded