Ok, the profiler to the rescue. Instantiating some exception sub-classes should tell us whether there is anything to be gained from a factory of some sort. A quick look does not show much going on on instantiation, so it is probably fine to create the appropriate sub-instance and set any useful aspects, and to pass that to the ouch-block.
Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: [EMAIL PROTECTED] Tel: (352) 846-1285 FAX: (352) 392-7029 >>> [EMAIL PROTECTED] 8/15/2008 3:48 PM >>> On Fri, Aug 15, 2008 at 8:51 PM, Bill Schwab <[EMAIL PROTECTED]> wrote: > I think the answer is probably to pass the *class* of the exception. > The default then simply sends the correct #signalWith: message with the > file name as an argument. Hmm, but the instance might hold additional information. Michael _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
