Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
One of the reasons I liked CodeView was the aforementioned hijacking of the keyboard interrupt - CodeView was smart enough to realise that had happened, set it back to the original value when hitting a breakpoint, and restore the hijacking value when you went back to running code, and even for each instruction as you single-stepped. Every other debugger was completely useless in this respect, as when you hit a breakpoint the keyboard no longer worked so you were stuck
Oh, and the fact that it buffered the screen memory, so you could flip back and forth between your graphics and the text-based debugger screen using F4, which made it a lot easier to work out what was going on if your drawing routines were going haywire, which they usually were on a first attempt
Then again, there was the joy of two monitors, a monochrome one and a CGA/EGA/VGA one.
Comment