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 handling, exceptions #1

Closed
jgrewe opened this issue Mar 6, 2013 · 3 comments
Closed

Error handling, exceptions #1

jgrewe opened this issue Mar 6, 2013 · 3 comments

Comments

@jgrewe
Copy link
Member

jgrewe commented Mar 6, 2013

We need a good way of error and exception handling

@stoewer
Copy link
Collaborator

stoewer commented Mar 6, 2013

For getter methods on attributes or related objects there should be a method to check for null values. And calling a getter of a null value should throw an exception.

e.g.
Block::name() can be checked with Block::nameIsNull() or Block::attrIsNull("name") to ensure that no EAttrIsNull exception will be thrown.

@gicmo
Copy link
Member

gicmo commented Mar 6, 2013

I would rather call them nameIsSet() or hasName() then IsNull.

@jgrewe
Copy link
Member Author

jgrewe commented May 14, 2013

just wrap things up and close this issue:
Policy is that we offer methods that allow to check for e.g. the existence of groups or attributes that should be called before trying to access the elements.
If one tries to access non-existing objects exceptions are thrown...

@jgrewe jgrewe closed this as completed May 14, 2013
stoewer pushed a commit that referenced this issue Feb 3, 2016
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

3 participants