• Examples
• Reference
  • The alpha::try proc
  • The try::level proc
  • The error::rethrow proc
• Known problems
• License and Disclaimer

• taciturn: display the error message in the message bar.
• terse: display the error message in a dialog.
• verbose: display the error message and the error code in a dialog.
• pedantic: display the error message, the error code, and whatever context is available through errorInfo in a window.

• log: display the error message, the error code, and whatever context is available through errorInfo in either the startup log or in the Tcl shell, if available, after alerting the user to the error.

Examples

alpha::try {
    error "this is the error" "" "this is the code"
}

• taciturn: reports this is the error in the message bar.
• terse: reports this is the error in a dialog.
• verbose: reports

  Message: "this is the error"
  Error Code: this is the code 
  

  in a dialog.
• pedantic: reports

  Message: "this is the error"
  Error Code: this is the code
  	# while executing
  error "this is the error" "" "this is the code"
  	# invoked from within
  alpha::try {error "this is the error" "" "this is the code"}
  

  in a window (the window is displayed in Tcl mode for better readability). Pedantic reports can get, well, pedantic very quickly, but can be useful guides for debug tracing.
• log: reports

  =======================
  alpha::try  error "this is the error" "" "this is the code" error
  this is the error
  	invoked from within
  alpha::try {error "this is the error" "" "this is the code"}
  

  in the Tcl shell (or in the startup log).

alpha::try {
	eval $script
} -onError {
	-34 {error::alertnote "Aughh!!! The disk is full!!!"}
	12* {error::alertnote "VOODOO error: $errorMsg"}
	default {}
}

set script {error "this is an error" "" "-34"}

set script {error "this is an error" "" "12005"}

alpha::try {
	eval $script
} -onError {
	default {}
}

catch $script

alpha::try {
	eval $script
} -onError {
	default error::rethrow
}

eval $script

alpha::try {
	eval $script
} -onError {
	-34 {error::alertnote "Aughh!!! The disk is full!!!"}
	{12[0-9][0-9][0-9]} {error::alertnote "VOODOO error: $errorMsg"}
	default {}
} -regexp

Reference

The alpha::try proc

    alpha::try script ?options?

-onError {pattern body ?pattern body ...?}

errorCode is compared to each pattern in order. When a match is found, body is executed in the stack frame that called alpha::try. If this option is missing, all errors will be displayed by the default routine.

-exact

Use exact matching when comparing errorCode to a pattern.

-glob

When matching errorCode to the patterns, use glob-style matching (i.e. the same as implemented by the [string match] command). This is the default.

-regexp

When matching errorCode to the patterns, use regular expression matching (i.e. the same as implemented by the [regexp] command).

-display

Override the user's setting for errorDisplay. Options are 'alertnote always', 'alertnote preferred', and 'window always'.

-reporting

Override the user's setting for errorReporting. Options are taciturn, terse, verbose, pedantic, and log.

-while

Short phrase to describe action taking place in event of an error.

-code

Match errorCode against the -onError patterns. This is the default.

-message

Match the errorMsg against the -onError patterns.

    alpha::try {
         error "" "" aaab
     } -onError {
       ^a.*b$ -
       b {format 1}
       a* {format 2}
       default {format 3}
     } -regexp

    alpha::try {
         error "" "" xyz
     } -onError {
       a
         -
       b
         {format 1}
       a*
         {format 2}
       default
         {format 3}
     }

    alpha::try {script} -depth n

    try::level n {script}

The try::level proc

    try::level level args

The error::rethrow proc

    error::rethrow

Known problems

License and Disclaimer

• Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
• Neither the name of Jonathan Guyer nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.