jdsl.core.api
Class CoreException
java.lang.Object
|
+--java.lang.Throwable
|
+--java.lang.Exception
|
+--java.lang.RuntimeException
|
+--jdsl.core.api.CoreException
- Direct Known Subclasses:
- BoundaryViolationException, ContainedLocatorException, EmptyContainerException, InvalidArgumentException, InvalidAttributeException, InvalidComparatorException, InvalidContainerException, InvalidEdgeException, InvalidElementException, InvalidKeyException, InvalidLocatorException, InvalidMethodCallException, InvalidPositionException, InvalidTreeException, NotEmptyContainerException, UncontainedLocatorException
- public abstract class CoreException
- extends java.lang.RuntimeException
At this writing I think that all the exceptions related to the core
data structures can be descended from one class. This is the class.
Future plan: to have a stack of messages, rather than a single message.
That way, an exception thrown at a low level can have a low-level
message associated with it, but if a higher-level function intercepts
it, the higher-level function can attach a more meaningful message.
But it may turn out that the low-level message was more helpful; a
stack would preserve both messages.
If you want the compiler to help you check special cases that you might
have missed, copy all the exceptions to your own directory, change
"extends RuntimeException" to "extends Exception," modify your
CLASSPATH to look first at your own directory, later here.
When you compile again, the compiler will give you a huge number of
"Exception must be caught or declared as thrown" errors, a small
fraction of which will point to special cases you have overlooked.
- Author:
- mdh
- See Also:
- Serialized Form
| Methods inherited from class java.lang.Throwable |
fillInStackTrace,
getLocalizedMessage,
getMessage,
printStackTrace,
printStackTrace,
printStackTrace,
toString |
| Methods inherited from class java.lang.Object |
equals,
getClass,
hashCode,
notify,
notifyAll,
wait,
wait,
wait |
CoreException
public CoreException(java.lang.String message)