ItemNotFound class: Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 56: Line 56:
<table class="syntaxTable">
<table class="syntaxTable">
<tr><th>%itemNotFound</th>
<tr><th>%itemNotFound</th>
<td>A reference to an instance of an <var>ItemNotFound</var> object.
<td>An <var>ItemNotFound</var> %variable which will refer to the newly created object.
</td></tr>
</td></tr>
<tr><th><var>%(ItemNotFound)</var></th><td>The class name in parentheses denotes a shared method.</td></tr>
<tr><th><var>%(ItemNotFound)</var></th><td>The class name in parentheses denotes a shared method.</td></tr>

Revision as of 20:26, 8 June 2011


An ItemNotFound exception indicates that a collection object search located no collection items that satisfy the selection criterion specified in the collection method that invoked the search. There are several searching methods, but only those that return a single found item produce an ItemNotFound exception.

This exception class has no properties. It is simply a notification that a valid search found no items that met the selection criterion.

The class's only method is the New constructor, which you would typically use with a User Language Throw statement to produce an ItemNotFound exception. For example:

throw %(itemNotFound):new

When working with the collection searching methods, remember that an exception is thrown only if there is a catcher for the exception. For example, if you expect one or no matches from your search, you might specify a block like the following:

try %terminationInfo = - %terminationList:findNextItem (eq(custId, %custid) ... process the termination info catch itemNotFound end try

On the other hand, if you always expect a match, you might want a program crash to result if you are wrong about the match, so you could leave out a Try/Catch.

The Try/Catch approach is slightly more efficient than a test for a zero result. Try generates no quads other than the branch around the catch block if the search succeeds. And in fact, you could put a Try around a loop and use the ItemNotFound exception to exit the loop:

%i = 0 try repeat forever %i = %colla:findNextItemNumber(<criterion>), start=%i) %obj = %colla(%i) ... process the object end repeat catch itemNotFound end try

The ItemNotFound class is available as of version 7.6.


The ItemNotFound methods

The following are the available ItemNotFound class methods.

MethodDescription
NewCreate a new ItemNotFound object

The methods in the class are described in the subsections that follow. In addition:


New constructor

Create a new ItemNotFound object (ItemNotFound class)

This callable constructor generates an instance of an ItemNotFound exception. The New method format follows:

Syntax

%itemNotFound = [%(ItemNotFound):]New

Syntax terms

%itemNotFound An ItemNotFound %variable which will refer to the newly created object.
%(ItemNotFound)The class name in parentheses denotes a shared method.