-
Notifications
You must be signed in to change notification settings - Fork 132
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
fix error handling in material parsing #122
base: master
Are you sure you want to change the base?
Conversation
@clalancette I just noticed that you also worked on more restrictive material parsing in #104. |
beb1e4e
to
9ebb53a
Compare
Ping |
9ebb53a
to
e787fc8
Compare
@scpeters, @clalancette, @sloretz |
There are 2 main things done here: 1. Check the return value from parseMaterial, parseLink, and parseJoint. While these can throw a ParseError exception, most often they return false when they fail to parse. 2. Revamp the error checking around those calls so that the code is indented a lot less. It is much easier to read this way. Signed-off-by: Chris Lalancette <[email protected]>
Just make the code flow easier to understand. Signed-off-by: Chris Lalancette <[email protected]>
Signed-off-by: Chris Lalancette <[email protected]>
Signed-off-by: Chris Lalancette <[email protected]>
We should consider the return value of parseMaterial(). Redefining the same material again, should be accepted. This often occurs when composing URDFs via xacro.
e787fc8
to
c5eaa16
Compare
We should consider the return value of parseMaterial() to react to plain parsing errors.
Redefining the same material again should be accepted though. This often occurs when composing URDFs via xacro.