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

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

1709995467

Гость


Was studying C++ when this answer came across. It suggests a [code]class[/code] with purely [code]static[/code] members with instantiation intentionally disabled.
But if the [code]class[/code] shall not be instantiated, is there a reason [code]namespace[/code] is not used instead? And if so or not, are there any other situations where using a [code]=delete[/code]d class constructor is better than using a [code]namespace[/code]?
I've read this answer and with my understanding, it says [code]namespace[/code] should not be used at all unless you really want to prevent name collisions, since [code]class[/code]es provides means for access control ([code]public[/code], [code]private[/code], [code]protected[/code]) 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 [code]class[/code] 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 [code]class[/code] with [code]=delete[/code]d constructor over a [code]namespace[/code].
 

Источник: [url]https://stackoverflow.com/questions/78132738/why-is-a-class-with-deleted-constructor-used-instead-of-namespace[/url]

Ответить

1 сообщение • Страница 1 из 1