You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 6, 2025. It is now read-only.
Upperclass currently halts all execution by calling error() whenever a fatal error is encountered during member lookup or access. For some users this may not be a desirable behavior.
We should permit the user to define a custom error handler within the class:
Upperclass currently halts all execution by calling error() whenever a fatal error is encountered during member lookup or access. For some users this may not be a desirable behavior.
We should permit the user to define a custom error handler within the class:
In addition, we should allow users to define custom error callbacks at the global level:
Users should be allowed to register multiple error handlers and upperclass will call each.
It is left up to the user when to halt the program when an upperclass error is encountered.
Default behavior to halt program execution upon an error should remain if no custom handlers are defined.