You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is a common practice for c++ libraries to avoid naming collisions.
For example, CDocument is a very common class name in C++ projects.
It could be namespace GumboQuery { or something like this.
The text was updated successfully, but these errors were encountered:
zenden2k
changed the title
Consider wrapping your code in a namespace
Consider wrapping library's code in a namespace
Jun 18, 2015
There's no need to shorten the namespace for user preference. That's why we have features like namespace short = some::long::possibly::nested::namespace; or namespace mypref = GumboQuery. :)
Namepace ought to be unique and spell out explicitly at full length what the unique namespace is.
Also imo this is something so simple, somebody could do this in 2 minutes and create a pull request instead of throwing the burden on the repo maintainer.
It is a common practice for c++ libraries to avoid naming collisions.
For example,
CDocument
is a very common class name in C++ projects.It could be
namespace GumboQuery {
or something like this.The text was updated successfully, but these errors were encountered: