Results for "Author: james boyd"

This class, written by James Boyd, is a logger/error handler that does many things: 1.) Displays errors to users when they occur 2.) Records the activities of the application as various subroutines get executed 3.) When a run-time error happens, it can fire off an e-mail to the developer, replete with routine name, error description, and even a dump of the app's execution stack at that point 4.) It can also maintain a text file which has the application's execution stack history There are two ways of using this error handling/logging class: 1.) Use it just for error trapping 2.) Use it also for logging the execution path of an application. Since it captures the exact occurrence of a logged activity down to the THOUSANDTH of a second, it can be extremely useful for performing performance/efficiency analysis on subroutines.

This class, written by James Boyd, is a logger/error handler that does many things: 1.) Displays errors to users when they occur 2.) Records the activities of the application as various subroutines get executed 3.) When a run-time error happens, it can fire off an e-mail to the developer, replete with routine name, error description, and even a dump of the app's execution stack at that point 4.) It can also maintain a text file which has the application's execution stack history There are two ways of using this error handling/logging class: 1.) Use it just for error trapping 2.) Use it also for logging the execution path of an application. Since it captures the exact occurrence of a logged activity down to the THOUSANDTH of a second, it can be extremely useful for performing performance/efficiency analysis on subroutines.

This class, written by James Boyd, is a logger/error handler that does many things: 1.) Displays errors to users when they occur 2.) Records the activities of the application as various subroutines get executed 3.) When a run-time error happens, it can fire off an e-mail to the developer, replete with routine name, error description, and even a dump of the app's execution stack at that point 4.) It can also maintain a text file which has the application's execution stack history There are two ways of using this error handling/logging class: 1.) Use it just for error trapping 2.) Use it also for logging the execution path of an application. Since it captures the exact occurrence of a logged activity down to the THOUSANDTH of a second, it can be extremely useful for performing performance/efficiency analysis on subroutines.

This class, written by James Boyd, is a logger/error handler that does many things: 1.) Displays errors to users when they occur 2.) Records the activities of the application as various subroutines get executed 3.) When a run-time error happens, it can fire off an e-mail to the developer, replete with routine name, error description, and even a dump of the app's execution stack at that point 4.) It can also maintain a text file which has the application's execution stack history There are two ways of using this error handling/logging class: 1.) Use it just for error trapping 2.) Use it also for logging the execution path of an application. Since it captures the exact occurrence of a logged activity down to the THOUSANDTH of a second, it can be extremely useful for performing performance/efficiency analysis on subroutines.

This class, written by James Boyd, is a logger/error handler that does many things: 1.) Displays errors to users when they occur 2.) Records the activities of the application as various subroutines get executed 3.) When a run-time error happens, it can fire off an e-mail to the developer, replete with routine name, error description, and even a dump of the app's execution stack at that point 4.) It can also maintain a text file which has the application's execution stack history There are two ways of using this error handling/logging class: 1.) Use it just for error trapping 2.) Use it also for logging the execution path of an application. Since it captures the exact occurrence of a logged activity down to the THOUSANDTH of a second, it can be extremely useful for performing performance/efficiency analysis on subroutines.

This class, written by James Boyd, is a logger/error handler that does many things: 1.) Displays errors to users when they occur 2.) Records the activities of the application as various subroutines get executed 3.) When a run-time error happens, it can fire off an e-mail to the developer, replete with routine name, error description, and even a dump of the app's execution stack at that point 4.) It can also maintain a text file which has the application's execution stack history There are two ways of using this error handling/logging class: 1.) Use it just for error trapping 2.) Use it also for logging the execution path of an application. Since it captures the exact occurrence of a logged activity down to the THOUSANDTH of a second, it can be extremely useful for performing performance/efficiency analysis on subroutines.

This class, written by James Boyd, is a logger/error handler that does many things: 1.) Displays errors to users when they occur 2.) Records the activities of the application as various subroutines get executed 3.) When a run-time error happens, it can fire off an e-mail to the developer, replete with routine name, error description, and even a dump of the app's execution stack at that point 4.) It can also maintain a text file which has the application's execution stack history There are two ways of using this error handling/logging class: 1.) Use it just for error trapping 2.) Use it also for logging the execution path of an application. Since it captures the exact occurrence of a logged activity down to the THOUSANDTH of a second, it can be extremely useful for performing performance/efficiency analysis on subroutines.

This class, written by James Boyd, is a logger/error handler that does many things: 1.) Displays errors to users when they occur 2.) Records the activities of the application as various subroutines get executed 3.) When a run-time error happens, it can fire off an e-mail to the developer, replete with routine name, error description, and even a dump of the app's execution stack at that point 4.) It can also maintain a text file which has the application's execution stack history There are two ways of using this error handling/logging class: 1.) Use it just for error trapping 2.) Use it also for logging the execution path of an application. Since it captures the exact occurrence of a logged activity down to the THOUSANDTH of a second, it can be extremely useful for performing performance/efficiency analysis on subroutines.

This class, written by James Boyd, is a logger/error handler that does many things: 1.) Displays errors to users when they occur 2.) Records the activities of the application as various subroutines get executed 3.) When a run-time error happens, it can fire off an e-mail to the developer, replete with routine name, error description, and even a dump of the app's execution stack at that point 4.) It can also maintain a text file which has the application's execution stack history There are two ways of using this error handling/logging class: 1.) Use it just for error trapping 2.) Use it also for logging the execution path of an application. Since it captures the exact occurrence of a logged activity down to the THOUSANDTH of a second, it can be extremely useful for performing performance/efficiency analysis on subroutines.

This class, written by James Boyd, is a logger/error handler that does many things: 1.) Displays errors to users when they occur 2.) Records the activities of the application as various subroutines get executed 3.) When a run-time error happens, it can fire off an e-mail to the developer, replete with routine name, error description, and even a dump of the app's execution stack at that point 4.) It can also maintain a text file which has the application's execution stack history There are two ways of using this error handling/logging class: 1.) Use it just for error trapping 2.) Use it also for logging the execution path of an application. Since it captures the exact occurrence of a logged activity down to the THOUSANDTH of a second, it can be extremely useful for performing performance/efficiency analysis on subroutines.

This class, written by James Boyd, is a logger/error handler that does many things: 1.) Displays errors to users when they occur 2.) Records the activities of the application as various subroutines get executed 3.) When a run-time error happens, it can fire off an e-mail to the developer, replete with routine name, error description, and even a dump of the app's execution stack at that point 4.) It can also maintain a text file which has the application's execution stack history There are two ways of using this error handling/logging class: 1.) Use it just for error trapping 2.) Use it also for logging the execution path of an application. Since it captures the exact occurrence of a logged activity down to the THOUSANDTH of a second, it can be extremely useful for performing performance/efficiency analysis on subroutines.

This class, written by James Boyd, is a logger/error handler that does many things: 1.) Displays errors to users when they occur 2.) Records the activities of the application as various subroutines get executed 3.) When a run-time error happens, it can fire off an e-mail to the developer, replete with routine name, error description, and even a dump of the app's execution stack at that point 4.) It can also maintain a text file which has the application's execution stack history There are two ways of using this error handling/logging class: 1.) Use it just for error trapping 2.) Use it also for logging the execution path of an application. Since it captures the exact occurrence of a logged activity down to the THOUSANDTH of a second, it can be extremely useful for performing performance/efficiency analysis on subroutines.

This class, written by James Boyd, is a logger/error handler that does many things: 1.) Displays errors to users when they occur 2.) Records the activities of the application as various subroutines get executed 3.) When a run-time error happens, it can fire off an e-mail to the developer, replete with routine name, error description, and even a dump of the app's execution stack at that point 4.) It can also maintain a text file which has the application's execution stack history There are two ways of using this error handling/logging class: 1.) Use it just for error trapping 2.) Use it also for logging the execution path of an application. Since it captures the exact occurrence of a logged activity down to the THOUSANDTH of a second, it can be extremely useful for performing performance/efficiency analysis on subroutines.

This class, written by James Boyd, is a logger/error handler that does many things: 1.) Displays errors to users when they occur 2.) Records the activities of the application as various subroutines get executed 3.) When a run-time error happens, it can fire off an e-mail to the developer, replete with routine name, error description, and even a dump of the app's execution stack at that point 4.) It can also maintain a text file which has the application's execution stack history There are two ways of using this error handling/logging class: 1.) Use it just for error trapping 2.) Use it also for logging the execution path of an application. Since it captures the exact occurrence of a logged activity down to the THOUSANDTH of a second, it can be extremely useful for performing performance/efficiency analysis on subroutines.