J_SCHULL@acc.haverford.edu (Jonathan Schull) (01/04/91)
(I presume the code would be version specific. I'm using TP 5.5 and 6.0.)
ts@uwasa.fi (Timo Salmi) (01/04/91)
In article <25383@adm.brl.mil> J_SCHULL@acc.haverford.edu (Jonathan Schull) writes: >(I presume the code would be version specific. I'm using TP 5.5 >and 6.0.) Trapping errors by one's own ExitProc has just been discussed at length in this group. One solution is to include a verbal explanation of the trapped error code in the procedure I presented here yesterday. Simple, but you'd have to do so typing of the code. The error codes are naturally in the manuals. Be caseful, though, if you put your procedure in an unit. You have to recover backwards from the trapping. See the references I gave for further details on that aspect. ................................................................... Prof. Timo Salmi (Moderating at anon. ftp site 128.214.12.3) School of Business Studies, University of Vaasa, SF-65101, Finland Internet: ts@chyde.uwasa.fi Funet: gado::salmi Bitnet: salmi@finfun
dave@tygra.ddmi.com (David Conrad) (01/05/91)
I have such code for TP 5.5. It installs an exit procedure which turns the error codes into messages. The error messages are reported by a function which is exported by the unit, so one can use them elsewhere. I'd be willing to pass this along to the net, if enough people feel that it's worth the bandwidth. (After all, one can type them all in onesself.) -- David R. Conrad | This space intentionally left... dave@tygra.ddmi.com | ...damn! -- = CAT-TALK Conferencing Network, Computer Conferencing and File Archive = - 1-313-343-0800, 300/1200/2400/9600 baud, 8/N/1. New users use 'new' - = as a login id. AVAILABLE VIA PC-PURSUIT!!! (City code "MIDET") = E-MAIL Address: dave@DDMI.COM
ts@uwasa.fi (Timo Salmi) (01/05/91)
In article <1991Jan5.084115.25880@tygra.ddmi.com> dave@tygra.ddmi.com (David Conrad) writes: >I have such code for TP 5.5. It installs an exit procedure which turns >the error codes into messages. The error messages are reported by a : Ditto. I am about to release the next update of my Turbo Pascal (4.0, 5.0, and 5.5) units collection (currently /pc/ts/tspas22.arc) and the new release contains a unit that turns on the verbal run-time error messages. ................................................................... Prof. Timo Salmi (Moderating at anon. ftp site 128.214.12.3) School of Business Studies, University of Vaasa, SF-65101, Finland Internet: ts@chyde.uwasa.fi Funet: gado::salmi Bitnet: salmi@finfun
zhou@brazil.psych.purdue.edu (Albert Zhou) (01/06/91)
I am definitely interested. Actually I posted an article asking how to make
floating point error message available to the program.
I am curious about this universal error processing redirection scheme. As I
know, some errors are fatal and need immediate processing or termination. If
what this unit does is to put an error message into a string, the error might
cause the system to crash.