Ask Your Question

Revision history [back]

I've commented on the issue you opened over at ros-industrial/kuka_experimental: ros-industrial/kuka_experimental/issues/120 - comment.

In short: --inorder is not needed on Jade and newer to enable the new xacro features. Those are enabled by default.

It was needed to enable "in order processing" of xacros on Jade. This was done to allow for a transition period in which users could test their xacros with the new xacro.

The --inorder flag is needed if you want to make use of the new xacro features on Indigo. This just makes Indigo xacro behave like Jade+ xacro.

I've updated the wiki on math expressions to suggest using --inorder, but I'm still a bit confused by the behavior and thought I'd bring it here in case there were further doc changes that might be helpful.

I hope it's now clear that --inorder is not needed to enable these new features, unless you are on Indigo. I would suggest to revert your changes, or clarify this is only needed for Indigo.


For some context, see ros/xacro#110, specifically Morgan's comment.

I've commented on the issue you opened over at ros-industrial/kuka_experimental: ros-industrial/kuka_experimental/issues/120 - comment.

In short: --inorder is not needed on Jade and newer to enable the new xacro features. Those are enabled by default.

It was needed to enable "in order processing" of xacros on Jade. This was done to allow for a transition period in which users could test their xacros with the new xacro.

The --inorder flag is needed if you want to make use of the new xacro features on Indigo. This just makes Indigo xacro behave like Jade+ xacro.

I've updated the wiki on math expressions to suggest using --inorder, but I'm still a bit confused by the behavior and thought I'd bring it here in case there were further doc changes that might be helpful.

I hope it's now clear that --inorder is not needed to enable these new features, unless you are on Indigo. I would suggest to revert your changes, or clarify this is only needed for Indigo.


For some context, see ros/xacro#110, specifically Morgan's comment.

Additionally, see ros/xacro#117 where this got merged.