One of the comments here is great and something we should always keep in mind:
> The source code also illustrates a major problem with such code: It doesn’t explain what problem exactly it’s trying to solve. That means the next programmer can’t easily ditch such nonsensical looking code because they can’t be sure that it isn’t solving some relatively widespread and legitimate problem. Testing won’t help too much because it can not be assumed that the hardware in question is actually available for testing.
⟩ it's still broken on my weitek coprocessor, please fix
• Thagomizing...
I'm trying to understand why the interrupt handler still isn't working for the user's Weitek 3167. It appears to be a timing bug. Maybe if I PUSH and POP AX a few dozen more times, the error trap will fall in the coprocessor's timing window?
One of the comments here is great and something we should always keep in mind:
> The source code also illustrates a major problem with such code: It doesn’t explain what problem exactly it’s trying to solve. That means the next programmer can’t easily ditch such nonsensical looking code because they can’t be sure that it isn’t solving some relatively widespread and legitimate problem. Testing won’t help too much because it can not be assumed that the hardware in question is actually available for testing.
⟩ it's still broken on my weitek coprocessor, please fix
• Thagomizing...
I'm trying to understand why the interrupt handler still isn't working for the user's Weitek 3167. It appears to be a timing bug. Maybe if I PUSH and POP AX a few dozen more times, the error trap will fall in the coprocessor's timing window?