Should I use static or a namespace?

Question

I have a dedicated HW register header file, I have created a namespace, like this, which holds all of my HW register addresses:

namespace{ const uint32_t Register1 = (0x00000000); const uint32_t Register2 = (0x00000004); const uint32_t Register3 = (0x00000008); const uint32_t Register4 = (0x0000000c); }

Is this considered better than using:

 static const uint32_t Register1 = (0x00000000); static const uint32_t Register2 = (0x00000004); static const uint32_t Register3 = (0x00000008); static const uint32_t Register4 = (0x0000000c);

I guess the point of namespaces is that we don't pollute the global namespace. Is that right?

I have one .cpp, which uses the header file.

C++11 I'd use a strongly typed enum

IdeaHat
– IdeaHat

2015-01-28 13:41:56 +00:00
Commented Jan 28, 2015 at 13:41 — IdeaHat
– IdeaHat, Commented Jan 28, 2015 at 13:41

Community · Accepted Answer · 2017-05-23 12:06:31Z

The two are essentially equivalent.

The global-static method was deprecated in C++03 ([depr.static]) in favour of unnamed namespaces, but then undeprecated by C++11 because everybody realised there is no objective benefit of one over the other in the general case.

However, for this, you may find an enum or enum class to be more manageable and idiomatic.

Angew is no longer proud of SO · Accepted Answer · 2015-01-28 14:01:36Z

These two are 100% equivalent, and they're also 100% equivalent to omitting both namespace and static:

const uint32_t Register1 = (0x00000000); const uint32_t Register2 = (0x00000004); const uint32_t Register3 = (0x00000008); const uint32_t Register4 = (0x0000000c);

The reason is simple - a const variable is static unless you explicitly declare it extern.

However, this looks like something where using an enumeration would be preferable.

Collectives™ on Stack Overflow

Should I use static or a namespace?

2 Answers 2

Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Linked

Related