delorie.com/archives/browse.cgi | search |
Xref: | news-dnh.mv.net comp.os.msdos.djgpp:887 |
Path: | news-dnh.mv.net!mv!news.sprintlink.net!cs.utexas.edu!bcm!newsfeed.rice.edu!rice!news!sandmann |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Request for feature in DJGPP V2 |
Date: | Tue, 11 Jul 1995 22:36:13 CDT |
Organization: | Rice University, Houston, Texas |
Lines: | 14 |
References: | <DBK4J9 DOT 779 AT jade DOT mv DOT net> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
Nntp-Posting-Host: | clio.rice.edu |
To: | djgpp AT sun DOT soe DOT clarkson DOT edu |
Dj-Gateway: | from newsgroup comp.os.msdos.djgpp |
> R: Could the developers of v2.0 consider a custom error message file that is > put into the program on compile-time ? > > e.g: > "You have found a bug in 'myprog'. DON'T PANIC. > Please make a screendump of this message and mail it to > developer AT somehost DOT somedomain ." First, you can use signal() in v2 to catch these bugs and do whatever you want, including recovery and continuation. Second, if that's not what you want, the source for dpmiexcp.c is included in V2, so you can replace the library version with your own version linked into the image.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |