Skip to content
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

[Discussion] Namespace #4

Open
drdanz opened this issue Jan 29, 2019 · 9 comments
Open

[Discussion] Namespace #4

drdanz opened this issue Jan 29, 2019 · 9 comments

Comments

@drdanz
Copy link
Member

drdanz commented Jan 29, 2019

We should enclose all the library in a namespace.
I also suggest we use c++11 inline namespace for versioning.

Proposals:

  • robotology
  • rbtlg (pronounced "robotology")
  • rtl
@aerydna
Copy link
Contributor

aerydna commented Jan 29, 2019

currently the namespace used for the only class(stub) present is robotology.

@drdanz
Copy link
Member Author

drdanz commented Jan 29, 2019

Personal opinion, it is a bit too long to write... It's fine with me anyway

@claudiofantacci
Copy link

Please: rtl. It's just what one would think after reading robotology-template-library, just as for the standard one.

@aerydna
Copy link
Contributor

aerydna commented Jan 30, 2019

my only concern is that with rtl there can be collision with other namespace more easily. otherwise it will be fine also for me

@claudiofantacci
Copy link

Are there any other rtd library out there that are likely to clash with this one? Otherwise I would always prefer brevity over lengthness for a namespace.

@aerydna
Copy link
Contributor

aerydna commented Jan 31, 2019

with all the possible interpretation of the acronym rtl like RunTimeLibrary, Real-TimeLibrary and so on, the risk of collision in the present or in the future is too high. I would exclude rtl. let's think some other abbreviation:

  • rbttl
  • rbtlg (don't like it but is fine)
  • robotl

other?

@claudiofantacci
Copy link

with all the possible interpretation of the acronym rtl like RunTimeLibrary, Real-TimeLibrary and so on, the risk of collision in the present or in the future is too high. I would exclude rtl. let's think some other abbreviation:

I still think that we should just go for rtl, but I see your point.

I would like to propose robotl that is a sound combination of robot, template library and library.
Otherwise rbtl.

@drdanz
Copy link
Member Author

drdanz commented Jan 31, 2019

Another concern is that any robotology related namespace could collide with other robotology repository. Perhaps we should choose a "standard" robotology namespace and use a sub-namespace. Or perhaps it's just overkill

@aerydna
Copy link
Contributor

aerydna commented Jan 31, 2019

i'm ok with both robotl and rbtl. @drdanz tiebreak!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants