-
Notifications
You must be signed in to change notification settings - Fork 8
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
Should we make this header-only? #10
Comments
@artivis this could shorten the |
Reviving this to point something small out: Beyond the normal considerations of header-only (longer compiles, but more chance for the compiler to optimize, etc), |
After a quick glance at the code... it's not using roscpp anymore and even tf2 is a very very marginal, case, used internally so probably dependencies could be reduced to urdf. Much larger of a chance for a header-only now! ;) |
We still need |
You are right... While the purist angel on one shoulder says "we could turn this into a C++ header-only library grabbing a string and returning error strings when failing" the little devil on the other one prefers convenience libraries to be...convenient. I side with the devil today |
Note that fetching the param from the param server ( As for the logging, one could replace it with an output argument e.g. I guess implementing the above two propositions implies important changes, @bmagyar looks like I'm playing on the angel of template side ;) |
I think we could simplify a couple of controllers but I'd opt for not linking to a lib for it.
Opinions @ros-controls/ros_control ?
The text was updated successfully, but these errors were encountered: