Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error/warning identification strings #21

Open
ehkropf opened this issue Jul 27, 2014 · 0 comments
Open

Error/warning identification strings #21

ehkropf opened this issue Jul 27, 2014 · 0 comments

Comments

@ehkropf
Copy link
Collaborator

ehkropf commented Jul 27, 2014

I would like to standardise the use of the identification strings used when calling error and warning. I have in use currently

  • CMT:InvalidArgument
  • CMT:NotDefined
  • CMT:OutOfTolerance
  • CMT:NotImplemented
  • CMT:BadIdea
  • CMT:BadThings

Admittedly the last two need rethought.

I'm thinking that if we keep this to a manageable list, it is easer for user code to look for errors from our code specifically, e.g., in try/catch blocks. A bit like we use MATLAB:UndefinedFunction in conformalmap for instance. Using identification strings along the lines of CMT:class:function seems to duplicate the work of the default error handler, as a console error tells you in which file the error originated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant