Following up on the first installment :

Slot wrapper objects do not directly call the C functions that theywrap up. Instead they check that they are being called with a self argument that is an instance of the type that they are wrapping,create a 'method-wrapper' object with the self memorized, andcall that .

We're not done yet, because there is another level of indirection:instead of directly calling the C function, the method-wrapper objectcalls a generic handler function for the particular sort

Someone from Coverity recently gave a talkto the local Unix hacks group abouttheir static analysis tools, and in the process got me to thinking aboutthe different types of bugs that I see.

As a first approximation, I think that I can split relatively commonbugs into three different classes:

• mistakes like using the wrong variable or off by one errors.
• oversights like forgetting to free memory or unlock a lock under somecircumstances.
• logic errors, where the code is accurately expressing your desire andyou got all the details right