Почему класс с конструктором `=delete`d используется вместо `namespace` ⇐ C++

[Гость]

Was studying C++ when this answer came across. It suggests a

Код: Выделить всё

class

with purely

Код: Выделить всё

static

members with instantiation intentionally disabled.
But if the

Код: Выделить всё

class

shall not be instantiated, is there a reason

Код: Выделить всё

namespace

is not used instead? And if so or not, are there any other situations where using a

Код: Выделить всё

=delete

d class constructor is better than using a

Код: Выделить всё

namespace

?
I've read this answer and with my understanding, it says

Код: Выделить всё

namespace

should not be used at all unless you really want to prevent name collisions, since

Код: Выделить всё

class

es provides means for access control (

Код: Выделить всё

public

,

Код: Выделить всё

private

,

Код: Выделить всё

protected

) and more features in general.
So if I were to answer my own question, it would be for better access control and just because it is a

Код: Выделить всё

class

does not necessarily mean it has to be instantiated somehwere, albiet not feeling much object-oriented. This is to check if the understanding is correct or not, and what are all the more reasons to prefer a

Код: Выделить всё

class

with

Код: Выделить всё

=delete

d constructor over a

Код: Выделить всё

namespace

.


Источник: https://stackoverflow.com/questions/781 ... -namespace