Name: rm29839 Date: 10/09/97
Right now the exceptions basically have
no (zero) information in them other
than their type e.g. ClassCastException
is just a humble class. OutOfMemoryError
has a similar problem.
This typically leads to serveral debugging
passes just to figure out exactly what
happened when in theory it seems reasonable
for the classes to tell more.
ClassCastException could also provide 2 class
refs - the class we tried to cast to and the
class we had.
OutOfMemory could tell the amount of memory
avail at that instant and the amount of
IndexOutOfBoundsException could provide
the object indexed, the size, and the
bad index that was tried.
I don't think there's much extra cost to this
kind of stuff and the advantage is that it
can [a] make the exceptions seem more valuable
and complete and [b] cut down on a pass or two.
Thanks for listening...
company - Lumos , email - ###@###.###