PeterBowman
commented
7 years ago A new, catch-all namespace was proposed by @jgvictores: roboticslab::. It might seem to be a bit lengthy; however, per Google's C++ Style Guide - General Naming Rules:
Give as descriptive a name as possible, within reason. Do not worry about saving horizontal space as it is far more important to make your code immediately understandable by a new reader. Do not use abbreviations that are ambiguous or unfamiliar to readers outside your project, and do not abbreviate by deleting letters within a word.
Although it doesn't concern namespaces explicitly (Function names, variable names, and filenames [...]), it might give a valuable pointer on how to approach this question. Remember that long namespaces can be shortened with the help of C++ namespace aliases:
namespace rl = roboticslab;
namespace teo = roboticslab::teo;More examples and some background: http://foonathan.net/blog/2016/01/26/namespace-alias.html.
jgvictores
rsantos88
munozyanez
As work on #2 goes on, we'll find out that former TEO-specific code is intented to target a wider range of robot platforms, thus rendering the omnipresent
teo::namespace quite inappropriate for common libraries. Proposed solutions:coin a new and catchy namespace only for this kind of libraries
create an omnibus prefix for every instance of Robotics Lab code to which existing and future namespaces would be appended:
rl::,rl::teo::,rl::asibot::,rl::amor::, etc.[x] openrave-yarp-plugins
[x] kinematics-dynamics
[x] vision
[x] speech
[x] tools
[x] gait
[x] Document at https://github.com/roboticslab-uc3m/best-practices