HandleError offers a method Process which is useful to handle application errors on a general level.
It has the following goals:
Create a namespace #.Crash and populate it with variables providing all sorts of information potentially important for analyzing the error. This namespace is also saved in a component file by default. This is mainly for application that cannot save an error workspace because threads are used.
- Creates an HTML page with essential information regarding the error.
Attempt to save an error workspace. In order to achieve that all running threads are killed; the main thread will always survive anyway. All options can be changed by setting variables in the namespace returned by CreateParms which can be passed as right argument to the main function Process. For defaults just pass an empty vector to Process.
You can make Process execute your own code by setting these two names in the parameter space:
logFunction is supposed to be the name of a monadic function that returns a shy result. The right argument is expected to process simple strings as well as vectors of strings.
customFns is supposed to be the name of a monadic function that returns a shy result. It can be used to do anything you like. The right argument is the namespace with the configuration settings, as returned by CreateParms. A typical application for this is sending an email to notify certain users about the crash.
However, if the log function is an instance method of a class then one cannot specify a name: it needs to be a reference. This can be achieved by specifying just the name of the method on logFunction but a reference pointing to an instanced or a namespace on logFunctionParent. Accordingly the same holds true for customFns and customFnsParent.
By default the variable errorFolder in a parameter space created by a call to CreateParms carries "Errors\". That means that HandleError attempts to write any files into this folder relative to whatever the current directory is. That means you have to make sure that this directory exists, otherwise it won't be able to create any file at all.
This example sets error trapping for an application so that HandleError.Process uses defaults (empty right argument):
⎕TRAP←(405 'E' '#.HandleError.Process ⍬')
This example uses the internal function SetTrap for setting ⎕TRAP:
#.HandleError.SetTrap checks whether the right argument is empty (early stage) or a parameter space and whether it is running under a development EXE or a runtime EXE and acts accordingly.
This example calls HandleError.CreateParms in order to create a command namespace and then modifies some of them. Note the usage of ⎕SHADOW in order to make sure that the ⎕TRAP statement can always "see" the right argument: it's kind of a global but at the same time it is local in the sense that it will disappear when the application finishes:
#.⎕SHADOW'HandleErrorParms' #.HandleErrorParms←#.HandleError.CreateParms #.HandleErrorParms.∆List addToMsg createHTML 1 customFns customFnsParent errorFolder Errors\ logFunction logFunctionParent off 1 returnCode 1 saveCrash 1 saveErrorWS 1 signal 0 trapInternalErrors 1 windowsEventSource ⎕TRAP←(405 'E' '#.HandleError.Process #.HandleErrorParms')
By editing or ⎕CRing the following function you can see what the command space contains together with a description.
ps←#.HandleError.CreateParms ⎕CR 'ps.∆Reference'
That would result in something similar to this:
- Boolean that defaults to 1. A 0 suppresses the creation of the HTML file
Name of a monadic function to be executed by "Process". Useful to send an email, for example. Either specify a fully qualified name of specify customFnsParent as well.
Reference pointing to a namespace or an instance where customFns can be found.
- Folder that keeps the component file (crash), the HTML page and the error WS
Name of the logging function to be used. Either specify a fully qualified name of specify logFunctionParent as well.
Reference pointing to a namespace or an instance where logFunction can be found.
- By default this function executes ⎕OFF with ""returnCode"" when in Runtime. A 0 suppressed this.
- The return code passed on to ⎕OFF
Boolean that defaults to 1. A 0 suppresses the creation of #.Crash & a component file saving this NS
- Boolean that defaults to 1. A 0 suppresses the creation of crash
- When "off" is 0 and "signal" is not 0 then "signal" is signaled by "Process". Can be used for a restart attempt.
- By default all internal errors are trapped: "Process" should never crash in an app.
- Name of the Windows Event Log to write to. Ignored when empty.
- Will be added to log file entries as well as Windows Event Log messages. Mainly for test cases
For bug reports, future enhancements and a full version history see HandleError/ProjectPage
HandleError needs version 13.0 of Dyalog APL.
Using an APLTree member
- If you just want to consume (use) an APLTree member then you have several choices:
Download it from its dedicated download page http://download.aplwiki.com/
Access it via FTP: ftp://ftp.aplwiki.com/APLTree/ with the user ID "anonymous". There is no password needed.
- Note that accessing it via ftp allows you to download older versions as well while the dedicated download page offers just the most current version.
If you want to contribute to an APLTree project see HowToContributeToTheAPLTreeProject for details.
Get the full project
If for some reason you need access to, say, the test cases then you need to get more then just the script (or application) itself.
HowToContributeToTheAPLTreeProject explains how to get a project onto your local machine. Just ignore any additional steps.