xacro --includes gives warning to use --inorder processing, which is not possible

[mrjogo]

Running the xacro --includes command gives the warning

xacro: Traditional processing is deprecated. Switch to --inorder processing!
To check for compatibility of your document, use option --check-order.
For more infos, see http://wiki.ros.org/xacro#Processing_Order

But running xacro --includes --inorder gives the error

xacro: error: options --inorder and --includes are mutually exclusive

[rhaschke]

I guess you would like to suppress the deprecation warning when the --includes option is used?

[mrjogo]

If that's the right resolution. I'm unclear if --includes somehow breaks the assumptions of --inorder processing. Ie, if a file is processed first with xacro --includes and then with xacro --inorder is it equivalent to just processing it with xacro --inorder.

[rhaschke]

Good point. Usually, xacro --includes | xacro --inorder should yield the same result as xacro --inorder.
However, if one uses ${} expressions for the filename argument of the <include> tag, this obviously requires prior (inorder) processing of the document to resolve the variable filename.
But combining both options, --inorder and --include, to cover this case as well, doesn't make sense: inorder-processing would already modify the document (evaluate expressions + macros), which is not intended by the --include option. That's why both options are mutually exclusive.

[mrjogo]

Ah, I understand now. Thanks!

[raequin]

Please tell me, if you're able, where I can learn about "traditional processing" vs using the --inorder flag.

[rhaschke]

Did you have a look into the wiki?