On 4/16/07, Charles Yeomans <[EMAIL PROTECTED]> wrote: > Shared methods belong to the class, not an object of the class. So > you call them using the syntax > > ClassName.MethodName.
Got it. I put together a little demo project using the code you included in your previous example, and it works great. I think it's a perfect solution for a situation where I'm creating new objects in a loop, and I want to test for them individually (in case there's one bad record in a bunch). In that case, a custom RuntimeException by itself terminates the method. This should allow me to test for a nil object in those cases so as to continue the loop. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
