www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1995/07/11/15:12:45

From: "A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk>
To: Anton Helm <tony AT nt DOT tuwien DOT ac DOT at>, djgpp AT sun DOT soe DOT clarkson DOT edu
Date: Tue, 11 Jul 1995 16:53:15 BST
Subject: Re: Request for feature in DJGPP V2

  Anton Helm <tony AT nt DOT tuwien DOT ac DOT at> wrote (Subject: Request for feature in
DJGPP V2):-

> 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 ." Tony

No need to alter the compiler! In your program, wherever logic reaches a place
which it never should, put in text to print out an appropriate `bug found'
error message. E.g. these bug-found statements in a text editor that I wrote:-

if(n!=_keyarray) MOAN("BUG: this is not a keyarray"); return (*k)[N];} ...
pr(CW,"BUG: %sbound to a %s",cw,f.n>0?"string":keysort[-f.n]); ...
pr(CW,f.s?"BUG: %sbound to empty string":"%sis unbound",cw); ...
Display="BUG: this key sequence is not complete"; return; ...
pr(CW,"BUG: %sbound to integer %1d",cw,f.i); Display=CW; return;} ...
  ... etc etc

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019