Formerly About Advanced Micro Devices Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Politics : Formerly About Advanced Micro Devices

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: James Yu who wrote (13200)	5/9/1997 11:38:00 PM
From: Paul Engel	of 1583995

James - Re: "Interceptors" The use of range checking and bounds checking is very common for good software design methodology. In fact, it is almost a necessity. For example - pull up a calculator application under Windows or a spreadsheeet. Then, try performing the following computation: 1/0. This illegal operation should be trapped by the application, notifying you of a "divide -by-zero" attempt. You should be gracefully returned to the point in the application where the operation was initiated. If not, the x86 (assuming the integer divide function - NOT THE FPU) will arttempt to perfrom the operation and you will generate a divide-by-zero hardware interrupt. In the earlier PCs, that would result in a hard re-booting of the computer, after a quick message was flashed on the screen. This is just one of MANY operations that are best trapped or intercepted by the application software to prevent unpredictable results from illegal operations. Intel's approach is expedient - no argument there. But it is also a valid, common approach to such problems. Paul Paul

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next