Watch, Follow, &
Connect with Us

Please visit our new home

Public Report
Report From: Conference/US/2006/Delphi    [ Add a report in this area ]  
Report #:  32418   Status: Open
Exceptional Exceptions by Jim McKeeth
Project:  Conference Build #:  No
Version:    1 Submitted By:   Christine Ellis
Report Type:  Suggestion / Enhancement Request Date Reported:  8/7/2006 3:16:39 PM
Severity:    Infrequently encountered problem Last Updated: 8/28/2006 1:37:25 PM
Platform:    All platforms Internal Tracking #:  
Resolution: None  Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: (16 Total Ratings)
4.00 out of 5
Total Votes: 5
Exceptional Exceptions by Jim McKeeth
TYPE: Regular Session
LEVEL: Intermediate
PREREQUISITES: Delphi programming experience
ABSTRACT: A great misconception by many developers is that an Exception is an error.  In actuality exceptions are a very powerful language feature which allows the movement of additional, unplanned information from a subroutine back to the routine that called it.  Consider the following function:

function test: boolean;

Upon first inspection it would appear that it is only able to return true and false.  Without exceptions that would be the case, but with exceptions this function can return a virtually unlimited array of results.  Essentially an exception is an unplanned condition was encountered - and by unplanned I mean one that does not fit the other language constructs.  

Once the exception = error myth is debunked we will move on to using exceptions.  

The first thing we will cover is how the integrated debugger handles exceptions.  This includes using breakpoints to enable and disable exception as well as specifying exceptions to ignore.  

Then we will look at the Exception object, descending from it, creating an instance of it and raising it.

Next we will look at some of the common special types of exceptions, including EAbort,  EAssertionFailed,  EAccessViolation, and some of the Indy exceptions.

We will briefly touch on exception handling using try, finally, except and global handlers.

Finally we will look at using exceptions in unusual ways to alter program execution and pass data back to the calling routine.

Upon completion of this session the attendee will see exceptions as an asset and not a hindrance to their software development.
SPEAKER BIOGRAPHY: Jim McKeeth is a software developer with over 15 years of experience in developing software and building online communities. He runs the Boise Software Developers Group, Idaho s longest running group of its kind. Jim works at Washington Group International as a Senior Software Engineer. He is a certified trainer and has shared the stage with some of the top trainers on the continent. Jim maintains a number of successful blogs and enjoys spending time with his wonderful family.
Steps to Reproduce:


Server Response from: ETNACODE01