Using the Provided try() Exception Handler - Revision history

76.184.213.234: /* See Also */

2010-11-03T13:46:57Z

‎See Also

76.184.213.234: /* See Also */

2010-11-03T13:46:08Z

‎See Also

Ximan: /* See Also */

2010-11-02T16:27:14Z

‎See Also

Ximan: /* See Also */

2010-11-02T16:26:50Z

‎See Also

Ximan at 06:15, 2 November 2010

2010-11-02T06:15:00Z

Ximan: /* See Also */

2010-11-02T06:14:00Z

‎See Also

Ximan at 06:13, 2 November 2010

2010-11-02T06:13:41Z

Ximan at 06:10, 2 November 2010

2010-11-02T06:10:26Z

Ximan: Created page with "The try library method is provided as a integrated replacement for pcall which reports and redirects error handling in the same fashion as the library itself. Use try to ..."

2010-11-02T06:07:59Z

Created page with "The try library method is provided as a integrated replacement for pcall which reports and redirects error handling in the same fashion as the library itself. Use try to ..."

New page

The [[try]] library method is provided as a integrated replacement for [[pcall]] which reports and redirects error handling in the same fashion as the library itself. Use try to wrap complex user functions wherever it is desirable to unify error reporting and or maintain script execution by silencing runtime errors that would otherwise halt the script.

To understand the available reporting and redirection modes, see the page on [http://www.easyuo.com/openeuo/wiki/index.php/Changing_Default_Error_Reporting_Mode changing the default error reporting and handling mode]. To set a specific mode, see [[slredirect]]. To understand what information is recorded with each detected error, see [[geterror]]. To clear all errors recorded internally and garbage collect, see [[clearerrors]].

[[try]] should be used at an appropriately high level in user code such that handler functions don't clutter the source and aren't nested to any degree. [[try]] isn't intended to be used low level, either directly on library calls or as a method of program flow micromanagement. Save the [[error]] function for throwing bona fide exceptions to the current course of execution; don't use try as a sort of if then statement. If you need C style switch case or a deep elseif alternative, see the [[case]] library method.

@@ Line 10: / Line 10: @@
 * [http://www.easyuo.com/openeuo/wiki/index.php/Changing_Default_Error_Reporting_Mode error reporting and handling modes]
 * [[clrerrors]]
 * [[geterror]]
 * [[slredirect]]

← Older revision		Revision as of 13:46, 3 November 2010
Line 20:		Line 20:

	* [[slredirect]]		* [[slredirect]]
		+
		+	* [[slverbosity]]

	* [[try]]		* [[try]]

@@ Line 8: / Line 8: @@
 * [http://www.easyuo.com/openeuo/wiki/index.php/Simplelib simplelib]
 * [[error]]
@@ Line 20: / Line 22: @@
 * [[try]]

← Older revision		Revision as of 16:26, 2 November 2010
Line 6:		Line 6:

	== See Also ==		== See Also ==
		+
		+	* [http://www.easyuo.com/openeuo/wiki/index.php/Simplelib simplelib]

	* [[error]]		* [[error]]

@@ Line 1: / Line 1: @@
 The [[try]] library method is provided as a integrated ''replacement'' for [[pcall]] which reports and redirects error handling in the same fashion as the library itself. Use try to wrap complex user functions wherever it is desirable to unify error reporting and or maintain script execution by silencing runtime errors that would otherwise halt the script.
-To understand the available reporting and redirection modes, see the page on changing the default [http://www.easyuo.com/openeuo/wiki/index.php/Changing_Default_Error_Reporting_Mode error reporting and handling mode].  To set a specific mode, see [[slredirect]].  To understand what information is recorded with each detected error, see [[geterror]].  To clear all errors recorded internally and garbage collect, see [[clearerrors]].
+To understand the available reporting and redirection modes, see the page on changing the default [http://www.easyuo.com/openeuo/wiki/index.php/Changing_Default_Error_Reporting_Mode error reporting and handling mode].  To set a specific mode, see [[slredirect]].  To understand what information is recorded with each detected error, see [[geterror]].  To clear all errors recorded internally and garbage collect, see [[clrerrors]].
 [[try]] should be used at an appropriately high level in user code such that handler functions don't clutter the source and aren't nested to any degree.  [[try]] isn't intended to be used low level, either directly on library calls or as a method of program flow micromanagement.  Save the [[error]] function for throwing bona fide exceptions to the current course of execution; don't use try as a sort of if then statement.  If you need C style switch case or a deep elseif alternative, see the [[case]] library method.
@@ Line 11: / Line 11: @@
 * [[pcall]]
-* [[clearerrors]]
+* [[clrerrors]]
 * [[geterror]]

@@ Line 1: / Line 1: @@
-The [[try]] library method is provided as a integrated replacement for [[pcall]] which reports and redirects error handling in the same fashion as the library itself. Use try to wrap complex user functions wherever it is desirable to unify error reporting and or maintain script execution by silencing runtime errors that would otherwise halt the script.
+The [[try]] library method is provided as a integrated --replacement-- for [[pcall]] which reports and redirects error handling in the same fashion as the library itself. Use try to wrap complex user functions wherever it is desirable to unify error reporting and or maintain script execution by silencing runtime errors that would otherwise halt the script.
 To understand the available reporting and redirection modes, see the page on [http://www.easyuo.com/openeuo/wiki/index.php/Changing_Default_Error_Reporting_Mode changing the default error reporting and handling mode].  To set a specific mode, see [[slredirect]].  To understand what information is recorded with each detected error, see [[geterror]].  To clear all errors recorded internally and garbage collect, see [[clearerrors]].
 [[try]] should be used at an appropriately high level in user code such that handler functions don't clutter the source and aren't nested to any degree.  [[try]] isn't intended to be used low level, either directly on library calls or as a method of program flow micromanagement.  Save the [[error]] function for throwing bona fide exceptions to the current course of execution; don't use try as a sort of if then statement.  If you need C style switch case or a deep elseif alternative, see the [[case]] library method.