C++ STL naming and common sense
-
Hi Notepad++ users and C++ developers!
Recently I raised a question on stackoverflow regarding naming of the C++ STL locks (such as lock_guard, scoped_lock, unique_lock and shared_lock).
It received negative votes:
https://stackoverflow.com/questions/76729014/why-c-stl-lock-names-are-so-abstract-unique-lock-shared-lock-scoped-lockI still believe that this question is valid and important from the positions of common sense.
When a lock has “unique” or “scoped” in its name, we probably should have important reasons and explanations related to what makes it “unique” or “scoped”. And, again, from my point of view, there are no such reasons and explanations from the positions of common sense where the name of the entity should describe the nature of this entity.
So I’m wondering: is there something wrong with my perception of what these things are and what they should be? Or is there some misunderstanding between my vision and vision of people on stackoverflow? Or is my question and its thoughts bad-formed? -
Rather off-topic for THIS forum…
-
You asked a rather opinion-based question (“why is X confusing” is completely in the eye of the beholder); as that’s not something that stackoverflow wants to cater to, they locked your post. If had phrased it such that you were asking for the technical details on the history of those terms, without injecting your opinions or asking for their opinions, and without requiring that any answer “justify” someone else’s decisions, it might not have been locked.
And your question has nothing to do with Notepad++, so it’s even less on-topic here than it was there. Hence, even though we appreciate your various contributions to Notepad++ and this Community, this specific topic is being locked here, as well.
-
P PeterJones locked this topic on
