Article View: comp.os.msdos.programmer
Article #335Critical Error handling in Borland C (BC++)
From: Eric A. Raymond
Date: Sun, 09 Aug 1992 20:49
Date: Sun, 09 Aug 1992 20:49
16 lines
1248 bytes
1248 bytes
Could someone elaborate on the use of harderr() in BC++?
I've looked at the examples but have some questions:
- what exactly do hardresume and hardretn do? (what is the difference?)
- what library functions are legal in the handler?
- BGI routines except those which allocate memory (which ones are they)?
- sprintf, (which stdio calls to avoid?)
- malloc most certainly would be evil?
- as far as non disk i/o errors (AH bit 7 = 1), is this where a
printer error would go? What tyoe sof errors would show up here
(examples show always abort and don't look to see if it is a
block or char device).
There is something about a DOS interrupt grater than 0x0C needed to be
Technical Details
Message-ID:
<1992Aug9.204913.21346@kronos.arc.nasa.gov>Path:
arc1-ca.pugleaf.net!sparky!uunet!sun-barr!ames!kronos.arc.nasa.gov!raymondShow Full Headers
Complete Article Headers
Newsgroups: comp.os.msdos.programmer,alt.msdos.programmer Path: arc1-ca.pugleaf.net!sparky!uunet!sun-barr!ames!kronos.arc.nasa.gov!raymond From: raymond@kronos.arc.nasa.gov (Eric A. Raymond) Subject: Critical Error handling in Borland C (BC++) Message-ID: <1992Aug9.204913.21346@kronos.arc.nasa.gov> Sender: usenet@kronos.arc.nasa.gov (Will Edgington, wedgingt@ptolemy.arc.nasa.gov) Nntp-Posting-Host: copernicus-arclan.arc.nasa.gov Organization: NASA Ames Research Center Date: Sun, 9 Aug 1992 20:49:13 GMT Lines: 16