I feel that following is the conclusion in C++ coding related to Class and access specifiers.
We know that we are hiding the data by making private or protected. But there are ways to access it.
The one who does not know how to access it will be confused but that really does not mean that we are restricting user to access it accidently.
The one who knows it will be accessing it and modify it.
So, OOPS is advantages in coding itself that beginner can’t modify the data.
So, is it not like that programmer has prepared logic in detail thinking that unknown user can’t access it?
But what if unknown coder is smart enough to change hidden data of class? Please take into consider that Smart coder I am referring to is the coder who does not willing to change unnecessary data willingly but he may feel to change it and as he is able, he is change it.
I am not sure how OOPs helps in this scenario. To conclude with, is not OOPs a simple agreed process we are following which may or may not help to protect data?
Ketan022
0
Newbie Poster
Recommended Answers
Jump to PostPrivate or protected in OOP has nothing to do with security and hiding secret data.
Read this thoroughly.
All 4 Replies
ddanbe
2,724
Professional Procrastinator
Featured Poster
deceptikon
1,790
Code Sniper
Team Colleague
Featured Poster
Ketan022
0
Newbie Poster
mike_2000_17
2,669
21st Century Viking
Team Colleague
Featured Poster
Be a part of the DaniWeb community
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.