1cfd3bbb56
Topic_CSS/Topic_HTML/Topic_JavaScript/Topic_Prompt/Topic_Comfyui 등 기존 카테고리 폴더를 정리하고, Topic_Graphic/Dev 등 신규 산출물과 Topics 내부 세션/메모리 기록을 동기화.
3.6 KiB
3.6 KiB
id, title, category, status, verification_status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, created_at, updated_at, review_reason, merge_history, tags, raw_sources, applied_in, github_commit
| id | title | category | status | verification_status | canonical_id | aliases | duplicate_of | source_trust_level | confidence_score | created_at | updated_at | review_reason | merge_history | tags | raw_sources | applied_in | github_commit | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| cpp-encapsulation | C++ Encapsulation | Programming_Language | draft | conceptual |
|
B | 0.86 | 2026-07-04 | 2026-07-04 |
|
|
CPP Encapsulation
🎯 한 줄 통찰 (One-line insight)
Encapsulation is the concrete APPLICATION of the previous chapter's abstract advice — "declare attributes private as often as you can" becomes actionable once you pair each private attribute with a public getter/setter method, meaning encapsulation isn't a separate new technique so much as the standard PATTERN for actually using private without making the data completely unreachable. [S1]
🧠 핵심 개념 (Core concepts)
- Encapsulation — hiding "sensitive" data by declaring class attributes
private, then providingpublicGET and SET methods for controlled access. [S1] - Setter method — a public method that ASSIGNS a value to a private attribute (
void setSalary(int s) { salary = s; }). [S1] - Getter method — a public method that RETURNS a private attribute's value (
int getSalary() { return salary; }). [S1] - Real-life analogy — an employee's salary is private (they can't change it directly); only the manager (a trusted method) can update or share it. [S1]
- Why encapsulate — better control of data (change one part without affecting others), increased data security. [S1]
📖 세부 내용 (Details)
- A private attribute accessed exclusively through a getter/setter pair:
class Employee { private: int salary; public: void setSalary(int s) { salary = s; } int getSalary() { return salary; } }; Employee myObj; myObj.setSalary(50000); cout << myObj.getSalary();. [S1]
⚖️ 모순 및 업데이트 (Contradictions & updates)
- 현재까지 발견된 모순 사항 없음 (No contradictions found in available sources).
🛠️ 적용 사례 (Applied in summary)
직원의 급여(salary)를 private으로 숨기고 setSalary()/getSalary()로만 접근하도록 하는 Employee 클래스 예제가 캡슐화의 대표 실전 활용 사례로 원문에 직접 제시됨. [S1]
💻 코드 패턴 (Code patterns)
A private attribute accessed only through public getter/setter methods (C++):
class Employee {
private:
int salary; // hidden
public:
void setSalary(int s) { salary = s; }
int getSalary() { return salary; }
};
int main() {
Employee myObj;
myObj.setSalary(50000);
cout << myObj.getSalary();
return 0;
}
✅ 검증 상태 및 신뢰도
- 상태: draft
- 검증 단계: conceptual
- 출처 신뢰도: B (W3Schools — widely used educational reference, not a primary standards body)
- 신뢰 점수: 0.86
- 중복 검사 결과: 신규 생성 (New discovery)
🔗 지식 그래프 (Knowledge Graph)
- 상위/루트: C++ Tutorial
- 관련 개념: CPP Access Specifiers, CPP Inheritance
- 참조 맥락: 접근 지정자 및 캡슐화 섹션 마지막 — 상속(Inheritance) 섹션으로 이어짐.
📚 출처 (Sources)
- [S1] W3Schools — C++ Encapsulation — https://www.w3schools.com/cpp/cpp_encapsulation.asp
📝 변경 이력 (Change history)
- 2026-07-04: Initial draft synthesized from the W3Schools "C++ Encapsulation" page (Astra wiki-curation, P-Reinforce v3.1 format).